Closed Bug 1208118 Opened 5 years ago Closed 4 years ago

SpiderMonkey SM-tc try jobs in TaskCluster failing to find proper compiler

Categories

(Taskcluster :: Services, defect)

defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jolesen, Unassigned)

References

Details

Try jobs launched with "-p sm-arm-sim" are failing because the compiler they find can't produce executables.

See for example this try build: https://treeherder.mozilla.org/#/jobs?repo=try&revision=23ef9729d025&exclusion_profile=false

It looks like the js/src/devtools/automation/autospider.py script is expecting $AUTOMATION to be set when it is looking for a compiler.

Log snippet: 

checking for gcc... /usr/bin/gcc -m32
checking whether the C compiler (/usr/bin/gcc -m32  ) works... no
configure: error: installation or configuration problem: C compiler cannot create executables.
------ config.log ------
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

configure:902: checking host system type
configure:923: checking target system type
configure:941: checking build system type
configure:1002: checking for gawk
configure:1276: checking for perl5
configure:1276: checking for perl
configure:2878: checking for gcc
configure:2991: checking whether the C compiler (/usr/bin/gcc -m32  ) works
configure:3007: /usr/bin/gcc -m32 -o conftest    conftest.c  1>&5
/usr/bin/ld: crt1.o: No such file: No such file or directory
collect2: ld returned 1 exit status
configure: failed program was:

#line 3002 "configure"
#include "confdefs.h"

main(){return(0);}
configure: error: installation or configuration problem: C compiler cannot create executables.
+ exit 2
+ BUILD_STATUS=2
+ mkdir -p /home/worker/artifacts/
+ cp -rL ./build/src/obj-spider/dist/bin/js ./build/src/obj-spider/dist/bin/jsapi-tests ./build/src/obj-spider/dist/bin/js-gdb.py /home/worker/artifacts/
cp: cannot stat `./build/src/obj-spider/dist/bin/js': No such file or directory
cp: cannot stat `./build/src/obj-spider/dist/bin/jsapi-tests': No such file or directory
cp: cannot stat `./build/src/obj-spider/dist/bin/js-gdb.py': No such file or directory
+ exit 2
[taskcluster] === Task Finished ===
[taskcluster] Unsuccessful task run with exit code: 2 completed in 183.841 seconds
Blocks: 1206187
Ok. In attempting to fix this, I realized that the taskcluster builds are only going to work on linux64 anyway. Well, *maybe* there's osx support too, but definitely not Windows. And we have spidermonkey builds on Windows.

I declare that it's time to give up on the taskcluster route, as much as it's supposed to be the future, and use buildbot instead.
(In reply to Steve Fink [:sfink, :s:] from comment #1)
> Ok. In attempting to fix this, I realized that the taskcluster builds are
> only going to work on linux64 anyway. Well, *maybe* there's osx support too,
> but definitely not Windows. And we have spidermonkey builds on Windows.

Actually...Firefox for Windows can be built on Taskcluster now :). http://petemoore.github.io/general/taskcluster/2015/09/30/building-firefox-for-windows-on-try-using-taskcluster.html has a detailed overview, but you can see a task definition for it here: https://tools.taskcluster.net/task-inspector/#ARNCa6tfSDuXMxkzxBjUTQ/

OS X is all supported through cross-compilation. You can see an example of that here: https://tools.taskcluster.net/task-inspector/#WKk9A15TRpO8qMjpOZuykQ/0. Ehsan talked about his experience a bit in http://ehsanakhgari.org/blog/2015-09-29/my-experience-adding-new-build-type-taskcluster and I think Ted has written up something somewhere too...
Moving to TaskCluster component...
Component: TaskCluster → Integration
Product: Testing → Taskcluster
Component: Integration → Platform and Services
Fixed a while back by some other bug. These are live and running happily atm.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Component: Platform and Services → Services
You need to log in before you can comment on or make changes to this bug.