427728 - talos burns regularly, probably because of an overlapped sync between push and pull

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P3)

Description

[Dan Mills [:thunder]]

Talos trunk qm-pmac02 is burning with an hdiutil problem:

01:48:13 URL:http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/bm-xserve08-trunk/firefox-3.0pre.en-US.mac.dmg [17630084/17630084] -> "firefox-3.0pre.en-US.mac.dmg" [1]
Initializing...
DIBackingStoreInstantiatorProbe: interface  0, score [32m     100[0m, 
[snip - lots more of the line above]
DIDiskImageInstantiatorProbe: nothing to select.
DIDiskImageNewWithBackingStore: probe fails to find appropriate CDiskImage class.
Attaching...
Error 106 (not recognized).
Finishing...
DIHLDiskImageAttach() returned 106
<CFDictionary 0x31eec0 [0xa08071c0]>{type = immutable, count = 0, capacity = 0, pairs = (
)}
hdiutil: attach failed - not recognized
rsync: link_stat "/Users/mozqa/talos-slave/mac-trunk/./mnt/*" failed: No such file or directory (2)
rsync error: some files could not be transferred (code 23) at /SourceCache/rsync/rsync-24/rsync/main.c(717)
hdiutil: detach failed - No such file or directory

Comment 1

[Nick Thomas [:nthomas] (UTC+12)]

I'm going to guess this talos box pulled a build as it was being replaced by the parent tinderbox (at about 1:40 PDT), leading to a corrupt tinderbox. Looking at the log for the current run, it got past hdiutil and seems to be running tests OK.

Comment 2

[Nick Thomas [:nthomas] (UTC+12)]

s/corrupt tinderbox/corrupt dmg/

It did recover on the next run.

Comment 3

[Dan Mills [:thunder]]

Indeed.  All good now.

Comment 4

[timeless]

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1207539840.1207541154.16560.gz

bzip2: Data integrity error
when decompressing.
	Input file = (stdin), output file = (stdout)

It is possible that the
compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.

You can use the `bzip2recover' program to attempt to recover data from undamaged sections of corrupted files.

tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now

Comment 5

[timeless]

glad it isn't blocking, but we still need the process/code fixed so that it doesn't happen in production.

Comment 6

[timeless]

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1207493880.1207495472.31677.gz http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1207449360.1207450656.10382.gz http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1207434480.1207436081.10412.gz http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1207434480.1207436094.10423.gz http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1207493880.1207495472.31677.gz

Comment 7

[Justin Dolske [:Dolske]]

Seems qm-mini-ubuntu02 just hit this twice in a row...

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1207713780.1207715069.12233.gz
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1207711680.1207714485.10930.gz

Comment 9

[alice nodelman [:alice] [:anode]]

Fixed by bug 291167.

Hourly builds are now dropped into their own dated directories - we can no longer hit a state where we are attempting to pull a build at the same time as a build is being dropped to the same location.