Closed Bug 718534 Opened 12 years ago Closed 12 years ago

talos-r3-xp-067 still failing jobs

Categories

(Release Engineering :: General, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 719892

People

(Reporter: nthomas, Assigned: bhearsum)

References

Details

(Whiteboard: IT to check what's wrong with it)

<philor>	oh, ffs, https://build.mozilla.org/buildapi/recent/talos-r3-xp-067
please remove that from production, remove it from the rack, and remove it from this earth, kthx

Disabled in slavealloc.
The first job in prod (a Rev3 WINNT 5.1 try debug test mochitests-2/5 on rev 3c7316b8b08b) hit this on the first rm_builddir step:
rm: cannot remove `build/xpcshell/tests/toolkit/mozapps/update/test_svc/unit/0000_svc_applyToDir/a/b/0/00/00png0.png': Permission denied
rm: cannot remove `build/xpcshell/tests/toolkit/mozapps/update/test_svc/unit/0000_svc_applyToDir/a/b/0/00/00text0': Permission denied
rm: cannot remove `build/xpcshell/tests/toolkit/mozapps/update/test_svc/unit/0000_svc_applyToDir/a/b/0/00/00text1': Permission denied
rm: cannot remove `build/xpcshell/tests/toolkit/mozapps/update/test_svc/unit/0000_svc_applyToDir/a/b/0/0exe0.exe': Permission denied
rm: cannot remove `build/xpcshell/tests/toolkit/mozapps/update/test_svc/unit/0000_svc_applyToDir/a/b/1/10/10text0': Permission denied
rm: cannot remove `build/xpcshell/tests/toolkit/mozapps/update/test_svc/unit/0000_svc_applyToDir/a/b/searchplugins/searchpluginspng0.png': Permission denied
rm: cannot remove `build/xpcshell/tests/toolkit/mozapps/update/test_svc/unit/0000_svc_applyToDir/a/b/searchplugins/searchpluginspng1.png': Permission denied
rm: cannot remove `build/xpcshell/tests/toolkit/mozapps/update/test_svc/unit/0000_svc_applyToDir/a/b/searchplugins/searchpluginstext0': Permission denied
rm: cannot remove `build/xpcshell/tests/toolkit/mozapps/update/test_svc/unit/0111_svc_applyToDir/a/b/2/20/20png0.png': Permission denied
rm: cannot remove `build/xpcshell/tests/toolkit/mozapps/update/test_svc/unit/0111_svc_applyToDir/a/b/2/20/20text0': Permission denied
rm: cannot remove `build/xpcshell/tests/toolkit/mozapps/update/test_svc/unit/0151_svc_applyToDir/a/b/2/20/20png0.png': Permission denied
rm: cannot remove `build/xpcshell/tests/toolkit/mozapps/update/test_svc/unit/0151_svc_applyToDir/a/b/2/20/20text0': Permission denied
rm: cannot remove `build/xpcshell/tests/toolkit/mozapps/update/test_svc/unit/0181_svc_applyToDir/a/b/2/20/20png0.png': Permission denied
rm: cannot remove `build/xpcshell/tests/toolkit/mozapps/update/test_svc/unit/0181_svc_applyToDir/a/b/2/20/20text0': Permission denied
rm: cannot remove `build/xpcshell/tests/toolkit/mozapps/update/test_svc/unit/0183_svc_applyToDir/a/b/2/20/20png0.png': Permission denied
rm: cannot remove `build/xpcshell/tests/toolkit/mozapps/update/test_svc/unit/0183_svc_applyToDir/a/b/2/20/20text0': Permission denied

In the mochitest log there is
 ERROR: Logon failure: unknown user name or bad password.
a couple of times. The step is purple and ends with:

INFO | runtests.py | Running tests: end.

command timed out: 1200 seconds without output, attempting to kill
SIGKILL failed to kill process
using fake rc=-1
program finished with exit code -1

remoteFailed: [Failure instance: Traceback from remote host -- Traceback (most recent call last):
Failure: exceptions.RuntimeError: SIGKILL failed to kill process
Assignee: nobody → armenzg
Priority: -- → P2
That was the job in progress when I disabled it in slavealloc. I've verified that the buildbot.tac file is now 
 print "SLAVE DISABLED; NOT STARTING"
 import sys
 sys.exit(0)
I don't what the heck I was looking at when I look at the jobs.
I was completely blinded by knowing that it syncs to OPSI but the maintenance service needs manual intervention.

My fault. I'm sorry. I will make sure they truly are ready if they ever come back (I have to make sure that there are no jobs that fail for permissions denied).
Priority: P2 → P3
Priority: P3 → P2
Depends on: 719892
This wasn't by the lack of manual intervention.

I hope we can figure out if it is a hard drive issue in bug 719892.
Assignee: armenzg → nobody
Priority: P2 → P3
Whiteboard: IT to check what's wrong with it
Assignee: nobody → bhearsum
Priority: P3 → --
Actually, this is tracked elsewhere already.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.