Closed Bug 783088 Opened 12 years ago Closed 12 years ago

"bash: screenresolution: command not found" when running tests on OS X opt builds

Categories

(Add-on SDK Graveyard :: General, defect)

All
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 773120

People

(Reporter: KWierso, Unassigned)

References

()

Details

On inbound now that bug 761620 has been backed out, I see that every OSX opt run of the Jetpack tests is orange because "screenresolutions: command not found". ========= Started 'bash -c ...' failed (results: 2, elapsed: 0 secs) (at 2012-08-15 12:51:50.105479) ========= bash -c 'screenresolution get && screenresolution list && system_profiler SPDisplaysDataType' in dir /Users/cltbld (timeout 1200 secs) watching logfiles {} argv: ['bash', '-c', 'screenresolution get && screenresolution list && system_profiler SPDisplaysDataType'] environment: Apple_PubSub_Socket_Render=/tmp/launch-sGDbIo/Render CVS_RSH=ssh DISPLAY=/tmp/launch-6d8qcJ/:0 HOME=/Users/cltbld LOGNAME=cltbld PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin PWD=/Users/cltbld SHELL=/bin/bash SSH_AUTH_SOCK=/tmp/launch-F3xAor/Listeners TMPDIR=/var/folders/Xr/Xr--yJnSEY0U11ET5NZuMU+++TM/-Tmp-/ USER=cltbld __CF_USER_TEXT_ENCODING=0x1F6:0:0 using PTY: False bash: screenresolution: command not found program finished with exit code 127 elapsedTime=0.038254 ========= Finished 'bash -c ...' failed (results: 2, elapsed: 0 secs) (at 2012-08-15 12:51:51.020404) ========= This has actually been happening before that bug was backed out, it was just masked by all of the brokenness elsewhere.
Kill the leopard, kill it with fire.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.