Created attachment 593600 [details] crash log on talos-r4-lion-069 cltblds-Mac-mini-260:unit cltbld$ pwd /Users/cltbld/talos-slave/test/build/xpcshell/tests/services/sync/tests/unit cltblds-Mac-mini-260:unit cltbld$ ls test_errorhandler.js test_errorhandler.js.log cltblds-Mac-mini-260:unit cltbld$ ls -l ls: test_errorhandler.js: No such file or directory ls: test_errorhandler.js.log: No such file or directory cltblds-Mac-mini-260:unit root# file test_errorhandler.js test_errorhandler.js: cannot open `test_errorhandler.js' (No such file or directory) The call to 'file' used tab complete. Logging into the machine using screensharing showed that there was a system crash in launchd Launchd was the process that crashed the system, i think. Syslog shows: Feb 1 13:06:06 cltblds-Mac-mini-260 com.apple.launchd.peruser.501 (com.apple.ReportCrash) <Warning>: Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self Feb 1 13:06:09 cltblds-Mac-mini-260 com.apple.launchd.peruser.501 (com.apple.launchctl.Aqua) <Warning>: Exited with code: 1
Created attachment 593601 [details] finder 'get info' window on the two files. Finder shows the files as present. I wonder if some weird permission is being set
Created attachment 593606 [details] File system is corrupt According to Disk Utility, this disk is corrupt.
Please reimage this slave
Assignee: nobody → server-ops-releng
Component: Release Engineering → Server Operations: RelEng
QA Contact: release → zandr
Summary: on lion test slaves there are files that show up for 'ls' but not cause errors in 'ls -l' → Please reimage talos-r4-lion-069
The machine has been reimaged. I also upgraded the EFI per bug 721386.
Assignee: server-ops-releng → nobody
Component: Server Operations: RelEng → Release Engineering
QA Contact: zandr → release
Priority: -- → P3
Summary: Please reimage talos-r4-lion-069 → Please return talos-r4-lion-069 to the production pool
returned back to production, saw green builds.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.