Closed Bug 682540 Opened 13 years ago Closed 13 years ago

Win32 comm-central lightning nightly builds failing since 19-Aug-2011

Categories

(Calendar :: Build Config, defect)

x86
Windows 7
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ssitter, Assigned: standard8)

References

(Depends on 1 open bug)

Details

Win32 comm-central lightning nightly builds failing since 19-Aug-2011 <http://tinderbox.mozilla.org/showbuilds.cgi?tree=CalendarTrunk> <https://ftp.mozilla.org/pub/mozilla.org/calendar/lightning/nightly/latest-comm-central/win32-xpi/> http://tinderbox.mozilla.org/showlog.cgi?log=CalendarTrunk/1314354094.1314365492.14928.gz#err0 make[7]: Leaving directory `/e/buildbot/comm-central-lightning-win32-nightly/build/objdir-tb/mozilla/parser/htmlparser/tests' make[6]: Leaving directory `/e/buildbot/comm-central-lightning-win32-nightly/build/objdir-tb/mozilla/parser/htmlparser' Could not create the directory: ..\..\..\..\..\..\_tests\testing\mochitest\tests\parser\htmlparser\tests\mochitest\html5lib_tree_construction\scripted: No such file or directory make[10]: *** [libs] Error 3
Hmm, sounds like bug 616542 is the culprit.
Sounds right, but I don't quite see if this is something we need to fix (and what exactly) or if core needs to be fixed. It seems tb/ffx builders are working.
Based on the date I think that the checkins for Bug 405007 might be the trigger for the problem to show up. What is the difference between the nightly and the hourly builders? Only the nightly builders show the error, the hourly builders are ok.
There is no difference I know of. Maybe a clobber helps, but I think we've tried this. I've clobbered the build dirs now.
Test failure means the build succeeded, lets continue in referenced bug
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Todays nightly build failed with the same _build_ error: http://tinderbox.mozilla.org/showbuilds.cgi?tree=CalendarTrunk As written before only the nightly builds are failing. (The hourly builds succeed but during xpcshell-tests one test fails.)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Sorry, you are right. I was too quick on that one.
Depends on: 616542
I've just nuked the -lightning part of the branch name on the buildbot master. This has the effect of reducing the location on disk on the slaves by 10 characters. I don't know if that'll be enough to fix this bug, but it should hopefully help. http://hg.mozilla.org/build/buildbot-configs/rev/4b121a84c4a2
Looks like there's some bustage fallout from my earlier changes and stop/starting of buildbot etc - I'm keeping an eye on it, it should in theory all go green.
The Nightly build just completed and is green. Tinderbox is lagging by a couple of hours at the moment, so it won't show up there just yet, but the build has been successful. When bug 616542 lands that'll just give us an extra safety margin.
Assignee: nobody → mbanner
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.