Closed Bug 622073 Opened 14 years ago Closed 14 years ago

[x86-64] "'wget -O ...' failed", after switch to buildbot v0.8

Categories

(SeaMonkey :: Release Engineering, defect)

x86_64
All
defect
Not set
major

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: sgautherie, Unassigned)

Details

Another x86_64 (Linux & MacOSX, SM 2.0 and trunk) build issue.
(Hopefully the last one.)

Example:
http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1293694579.1293698828.31569.gz&fulltext=1
OS X 10.6 comm-central-trunk build on 2010/12/29 23:36:19
{
======== BuildStep started ========
'wget -O ...' failed
=== Output ===
wget -O codesize-auto-old.log http://stage.mozilla.org/pub/mozilla.org/seamonkey/tinderbox-builds/comm-central-trunk-macosx64//codesize-auto.log
...
--00:46:24--  http://stage.mozilla.org/pub/mozilla.org/seamonkey/tinderbox-builds/comm-central-trunk-macosx64//codesize-auto.log
           => `codesize-auto-old.log'
Resolving stage.mozilla.org... 63.245.208.158
Connecting to stage.mozilla.org|63.245.208.158|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
00:46:24 ERROR 404: Not Found.

program finished with exit code 1
elapsedTime=0.146157
=== Output ended ===
======== BuildStep ended ========
}

I don't check/know whether SeaMonkey should not access stage.mozilla.org or is missing some rights or doesn't like '//' or the file isn't there or whatever...

PS: Ftr, this error orange was kind of "hidden" on TBPL by bug 621034, so I didn't care to file it until the later was fixed.
Flags: in-testsuite-
No longer depends on: 621034
(In reply to comment #0)
> PS: Ftr, this error orange was kind of "hidden" on TBPL by bug 621034, so I
> didn't care to file it until the later was fixed.

s/orange/red/, fwiw.
Thanks for filing, but that's not really a bug, it's expected that this fails the first time it's being tried, IIRC, it should succeed the following times. It's just that the file doesn't exist if none has been uploaded by another cycle yet.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
Right: next builds are green :->
Status: RESOLVED → VERIFIED
V.Invalid
You need to log in before you can comment on or make changes to this bug.