Edgewall Software
Modify

Opened 14 years ago

Last modified 14 years ago

#559 new defect

bitten-slave suddenly stops working and returns a 404 error

Reported by: pfote@… Owned by:
Priority: major Milestone: 0.6.1
Component: General Version: 0.6b2
Keywords: git sorting revision 404 Cc:
Operating System: BSD

Description

we had the effect that a working configuration suddenly stopped working, bitten-slave returned something like:

bittenslave@dev1:~$ bitten-slave -v -f slave.ini http://trac-host:8000/builds
[INFO    ] Slave launched at 2010-04-12 11:36:41
[DEBUG   ] Enabling authentication with username 'bitten'
[DEBUG   ] Performing basic/digest authentication
[DEBUG   ] Sending HEAD request to 'http://trac-host:8000/login'
[DEBUG   ] Configured packages: {}
[DEBUG   ] Sending slave configuration: <slave version="2" name="dev1"><platform processor="i686">i686</platform><os version="Debian5.0" family="posix">Linux</os></slave>
[DEBUG   ] Sending POST request to 'http://trac-host:8000/builds'
[DEBUG   ] Server returned error 404: Not Found (no message available)
[ERROR   ] HTTP Error 404: Not Found
[DEBUG   ] Removing working directory /tmp/bittenWiTPzF
[INFO    ] Slave exited at 2010-04-12 11:36:44

it turned out that a changeset was not found in the git repository:

Apr 12 11:08:17 f1-gitserv Trac[PyGIT] DEBUG: requested PyGIT.Storage instance 148630572 for '/home/git/repositories/norris.git'
Apr 12 11:08:17 f1-gitserv Trac[git_fs] INFO: enabled CachedRepository for '/home/git/repositories/norris.git'
Apr 12 11:08:17 f1-gitserv Trac[queue] INFO: Enqueuing build of configuration "norris" at revision [9e093b1fb00a212167c752b9dd01a8aff9cd983a] on Linux Debian 5.0 i686
Apr 12 11:08:18 f1-gitserv Trac[queue] INFO: Enqueuing build of configuration "norris" at revision [e078a418a3a35ae6889775f515423a0f1c95e9d4] on Linux Debian 5.0 i686
Apr 12 11:08:18 f1-gitserv Trac[queue] INFO: Enqueuing build of configuration "norris" at revision [3e964b16b97cfed970cacd8cb7fe1aefc6f7d08b] on Linux Debian 5.0 i686
Apr 12 11:08:18 f1-gitserv Trac[queue] INFO: Enqueuing build of configuration "norris" at revision [963c37b7676156854ce0b70c164f41d5d61b7b2f] on Linux Debian 5.0 i686
Apr 12 11:08:18 f1-gitserv Trac[queue] INFO: Enqueuing build of configuration "norris" at revision [092de77afa24ba2fdb864b69603c12b2861a62f5] on Linux Debian 5.0 i686
Apr 12 11:08:18 f1-gitserv Trac[queue] INFO: Enqueuing build of configuration "norris" at revision [e7fc21700b20a3e7e9ff985f4b56cf095dbb5053] on Linux Debian 5.0 i686
Apr 12 11:08:18 f1-gitserv Trac[queue] INFO: Enqueuing build of configuration "norris" at revision [2c14778a1b38407365bda08d3d3e450950e71833] on Linux Debian 5.0 i686
Apr 12 11:08:18 f1-gitserv Trac[queue] INFO: Enqueuing build of configuration "norris" at revision [f14108f4704540af3a9ed06374433d5196c7e7bd] on Linux Debian 5.0 i686
Apr 12 11:08:18 f1-gitserv Trac[queue] INFO: Enqueuing build of configuration "norris" at revision [af0dd030328361ebc617f7cba904b0af8db0d345] on Linux Debian 5.0 i686
Apr 12 11:08:20 f1-gitserv Trac[queue] INFO: Enqueuing build of configuration "norris" at revision [15956a4fd8d13081a82451831a7bd5546418573d] on Linux Debian 5.0 i686
Apr 12 11:08:20 f1-gitserv Trac[main] WARNING: HTTPNotFound: 404 No such changeset (No changeset 15956a4fd8d13081a82451831a7bd5546418573d in the repository)
Apr 12 11:08:20 f1-gitserv Trac[chrome] DEBUG: Prepare chrome data for request

however, that changeset DOES exist in the repository.

we're running bitten 0.6b2 on the following trac (debian lenny 5.0.4):

Trac:	0.11.5
Python:	2.5.2 (r252:60911, Jan 24 2010, 14:53:14) [GCC 4.3.2]
setuptools:	0.6c8
SQLite:	3.5.9
pysqlite:	2.3.2
Genshi:	0.5.1
Pygments:	1.1.1
Bitten:	0.6b2
GIT:	1.5.6.5
jQuery:	1.2.6

unfortunatly i'm not able to offer you guys the repository in question for reproduction, but i'm willing to test patches

Attachments (0)

Change History (1)

comment:1 Changed 14 years ago by anatoly techtonik <techtonik@…>

Exiting slaves is a problem here too. Bitten slaves should have an option to report by email when they fail and exit.

Add Comment

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The ticket will remain with no owner.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.