Modify ↓
#46 closed defect (fixed)
Fail to build the first revision
Reported by: | Otavio Salvador <otavio@…> | Owned by: | cmlenz |
---|---|---|---|
Priority: | major | Milestone: | 0.5 |
Component: | Build slave | Version: | 0.4 |
Keywords: | Cc: | ||
Operating System: |
Description
Looks like bitten can't build the r1 :(
Look bellow:
[DEBUG ] Handling frame [MSG 1 2 . 660 471] [DEBUG ] Sending frame [RPY 1 2 . 342 184] [DEBUG ] Handling frame [MSG 1 3 . 1131 148] [DEBUG ] Received snapshot archive: /tmp/bittenr4UIY7/trunk_r1.tar.bz2 [ERROR ] file could not be opened successfully Traceback (most recent call last): File "/usr/lib/python2.3/asyncore.py", line 69, in read obj.handle_read_event() File "/usr/lib/python2.3/asyncore.py", line 390, in handle_read_event self.handle_read() File "/usr/lib/python2.3/asynchat.py", line 136, in handle_read self.found_terminator() File "/usr/lib/python2.3/site-packages/bitten-0.4dev-py2.3.egg/bitten/util/beep.py", line 279, in found_terminator File "/usr/lib/python2.3/site-packages/bitten-0.4dev-py2.3.egg/bitten/util/beep.py", line 312, in _handle_frame File "/usr/lib/python2.3/site-packages/bitten-0.4dev-py2.3.egg/bitten/util/beep.py", line 466, in handle_data_frame File "/usr/lib/python2.3/site-packages/bitten-0.4dev-py2.3.egg/bitten/slave.py", line 140, in handle_msg File "/usr/lib/python2.3/site-packages/bitten-0.4dev-py2.3.egg/bitten/util/archive.py", line 106, in unpack File "/usr/lib/python2.3/tarfile.py", line 903, in open raise ReadError, "file could not be opened successfully" ReadError: file could not be opened successfully
Attachments (0)
Change History (3)
comment:1 Changed 19 years ago by cmlenz
- Status changed from new to assigned
comment:2 Changed 19 years ago by Otavio Salvador <otavio@…>
This happens when the tarball is empty so makes sense to avoid to build if trunk or the repository path is empty.
comment:3 Changed 19 years ago by cmlenz
- Resolution set to fixed
- Status changed from assigned to closed
Should be fixed in [206].
The build for your rev 1 has already been scheduled though, so you'll have to remove it from the database manually:
$ sqlite3 /path/to/projenv/db/trac.db sqlite> DELETE FROM bitten_build WHERE rev='1';
Note: See
TracTickets for help on using
tickets.
Can you trying unpacking the file manually, both on the slave (at /tmp/bittenr4UIY7/trunk_r1.tar.bz2) and on the master (at /path/to/projenv/snapshots/trunk_r1.tar.bz2)?
Are the two files exactly the same?