1299191 - Intermittent make[1]: *** [/home/worker/workspace/build/src/js/src/configure] Error 1

Status: RESOLVED FIXED

(Taskcluster :: General, defect)

Description

[Treeherder Bug Filer]

Filed by: rvandermeulen [at] mozilla.com

https://treeherder.mozilla.org/logviewer.html#?job_id=2778356&repo=autoland

https://queue.taskcluster.net/v1/task/I0Ng4haOQNyZ_hGXhy1HwQ/runs/0/artifacts/public%2Flogs%2Flive_backing.log

I'm assuming this is due to a stale cache or something, so calling it a Taskcluster bug.

Comment 1

[Dustin J. Mitchell [:dustin] (he/him)]

checking for localeconv... (cached) yes
updating cache ./config.cache
creating ./config.data
Creating config.status
Reticulating splines...
Finished reading 40 moz.build files in 0.07s
Processed into 221 build config descriptors in 0.17s
RecursiveMake backend executed in 0.12s
  139 total backend files; 139 created; 0 updated; 0 unchanged; 0 deleted; 8 -> 36 Makefile
FasterMake backend executed in 0.00s
  4 total backend files; 4 created; 0 updated; 0 unchanged; 0 deleted
Total wall time: 0.40s; CPU time: 0.40s; Efficiency: 101%; Untracked: 0.03s
make: Entering directory `/home/worker/workspace/build/src/obj-spider'
make: Leaving directory `/home/worker/workspace/build/src/obj-spider'
make: Entering directory `/home/worker/workspace/build/src/obj-spider'
make[1]: Entering directory `/home/worker/workspace/build/src/obj-spider'
STOP!  /home/worker/workspace/build/src/js/src/old-configure.in has changed, and your configure is out of date.
Please rerun autoconf and re-configure your build directory.
To ignore this message, touch "/home/worker/workspace/build/src/js/src/configure",
but your build might not succeed.

Comment 2

[Dustin J. Mitchell [:dustin] (he/him)]

So, all of the spidermonkey builds share the same cache name, `level-{level}-{project}-build-spidermonkey-workspace`.  Would different spidermonkey builds confuse one another this way?  Should we use different workspace caches for them?

Comment 4

[Intermittent Failures Robot]

21 automation job failures were associated with this bug in the last 7 days.

Repository breakdown:
* autoland: 19
* mozilla-inbound: 2

Platform breakdown:
* linux64: 21

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1299191&startday=2016-09-12&endday=2016-09-18&tree=all

Comment 5

[Steve Fink [:sfink] [:s:]]

I don't understand how the cache is used. I sort of assumed it was where the ccache was stored. But if it's used to hold the actual objdir, then... well, I wouldn't *think* it should cause any problems, but it has been broken in the past (where rerunning configure with different arguments required a clobber.)

So if that's the case, then it would be safer to have the variant or the job name in the cache name.

Comment 6

[Dustin J. Mitchell [:dustin] (he/him)]

Yes, it is for the objdir.  It sounds like separating those would be a good idea.

Comment 7

[Intermittent Failures Robot]

7 automation job failures were associated with this bug in the last 7 days.

Repository breakdown:
* mozilla-inbound: 5
* autoland: 2

Platform breakdown:
* linux64: 7

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1299191&startday=2016-09-19&endday=2016-09-25&tree=all

Comment 8

[Intermittent Failures Robot]

9 automation job failures were associated with this bug in the last 7 days.

Repository breakdown:
* autoland: 9

Platform breakdown:
* linux64: 9

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1299191&startday=2016-09-26&endday=2016-10-02&tree=all

Comment 9

[Greg Arndt [:garndt]]

Issue has not happened in over a month, and the bug (1302429) referenced has been fixed.  I think we can call this resolved.  Please reopen if the issue occurs again.