555049 - TryServer failure while checking out talos: "cvs [checkout aborted]: cannot rename file CVS/Entries.Backup to CVS/Entries: File exists"

Status: RESOLVED WORKSFORME

(Release Engineering :: General, defect, P2)

Description

[Daniel Holbert [:dholbert]]

http://tinderbox.mozilla.org/showlog.cgi?log=MozillaTry/1269550196.67.1269550376.11841.gz
WINNT 6.0 try talos svg on 2010/03/25 13:49:56

tinderbox: tree: MozillaTry
tinderbox: builddate: 1269550196.67
tinderbox: status: busted
tinderbox: build: WINNT 6.0 try talos svg
tinderbox: errorparser: unix
tinderbox: binaryurl: 
tinderbox: logcompression: bzip2
tinderbox: logencoding: base64
tinderbox: END

{
U talos/page_load_test/jss/object-regexp-112.html
U talos/page_load_test/jss/object-regexp-113.html
U talos/page_load_test/jss/object-regexp-114.html
U talos/page_load_test/jss/object-regexp-115.html
U talos/page_load_test/jss/object-regexp-116.html
U talos/page_load_test/jss/object-regexp-117.html
U talos/page_load_test/jss/object-regexp-118.html
U talos/page_load_test/jss/object-regexp-119.html
U talos/page_load_test/jss/object-regexp-12.html
U talos/page_load_test/jss/object-regexp-120.html
cvs [checkout aborted]: cannot rename file CVS/Entries.Backup to CVS/Entries: File exists
program finished with exit code 1
}

Any idea what might have caused this?

Comment 1

[Chris Cooper [:coop] (he/him)]

Doing some investigation on the slave (qm-pvista-try09) now.

Comment 2

[Chris Cooper [:coop] (he/him)]

Didn't find anything out of the ordinary ownership or permissions-wise, and we've had successful svg runs on this box since the initial problem. Tagging the slave as potentially bad and moving on.

Comment 3

[Chris AtLee [:catlee]]

Could the slave have failed to clean up properly before?

Comment 4

[Chris Cooper [:coop] (he/him)]

(In reply to comment #3)
> Could the slave have failed to clean up properly before?

Nothing in the logs from the previous svg run, but we don't clean up at the end of talos runs like we do for e.g. nightlies. The intial cleanup step for the build in question had no errors either.