Opened 15 years ago
Closed 14 years ago
#4172 closed bug (fixed)
svn stop while checking out ruby source tree
| Reported by: | oco | Owned by: | axeld |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | Network & Internet/TCP | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
This problem occurs while checking out ruby source tree using this command :
svn co http://svn.ruby-lang.org/repos/ruby/trunk ruby
I often have this problem with my old laptop, but only with this specific source tree. No problem with Haiku's or freepascal's one. I was able to reproduce it with latest haiku image (haiku-pre-alpha-hrev32040-vm.zip) in vmware.
I have attached the serial output from the vmware session. Maybe there is a problem with this specific source tree, but there is a READ FAULT at 0xffffffff in the back trace (see serial output). So, it may be a problem in Haiku. After a long long wait (many minutes), the connection usually time out and SVN print this error :
"Could not read response body: Socket is not connected"
Any ideas ?
Attachments (1)
Change History (5)
by , 15 years ago
| Attachment: | haiku-serial-port.txt added |
|---|
comment:1 by , 15 years ago
| Component: | - General → Network & Internet/TCP |
|---|
comment:3 by , 14 years ago
While looking at my old bugs, i have successfully checkout the ruby source tree two times. So, i think this ticket is solved now. Tested in hrev35937.
comment:4 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
| Version: | R1/pre-alpha1 → R1/Development |
This has probably been fixed in hrev35468, thanks for the update.
It shows an interesting Tracker bug, at least ;-)
I could imagine that this is a TCP problem, or at least network related. Someone should look into it as long as it is reproducible.