Closed Bug 1549983 Opened 5 years ago Closed 5 years ago

Perma mozbuild.configure.options.InvalidOptionError: --enable-profile-use is not available in this configuration

Categories

(Firefox Build System :: General, defect, P5)

defect

Tracking

(firefox-esr60 unaffected, firefox67 unaffected, firefox68 fixed, firefox69 fixed)

RESOLVED FIXED
mozilla69
Tracking Status
firefox-esr60 --- unaffected
firefox67 --- unaffected
firefox68 --- fixed
firefox69 --- fixed

People

(Reporter: intermittent-bug-filer, Assigned: mshal)

References

Details

(Keywords: intermittent-failure, regression)

Filed by: hskupin [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer.html#?job_id=245326989&repo=try
Full log: https://queue.taskcluster.net/v1/task/BuwGj6CPRCeRMJH86E1Klg/runs/0/artifacts/public/logs/live_backing.log


[task 2019-05-08T12:59:01.835Z] 12:59:01 INFO - checking whether cross compiling... no
[task 2019-05-08T12:59:01.891Z] 12:59:01 ERROR - Traceback (most recent call last):
[task 2019-05-08T12:59:01.891Z] 12:59:01 INFO - File "/builds/worker/workspace/build/src/configure.py", line 132, in <module>
[task 2019-05-08T12:59:01.891Z] 12:59:01 INFO - sys.exit(main(sys.argv))
[task 2019-05-08T12:59:01.891Z] 12:59:01 INFO - File "/builds/worker/workspace/build/src/configure.py", line 38, in main
[task 2019-05-08T12:59:01.891Z] 12:59:01 INFO - sandbox.run(os.path.join(os.path.dirname(file), 'moz.configure'))
[task 2019-05-08T12:59:01.891Z] 12:59:01 INFO - File "/builds/worker/workspace/build/src/python/mozbuild/mozbuild/configure/init.py", line 441, in run
[task 2019-05-08T12:59:01.891Z] 12:59:01 INFO - self._value_for(option)
[task 2019-05-08T12:59:01.891Z] 12:59:01 INFO - File "/builds/worker/workspace/build/src/python/mozbuild/mozbuild/configure/init.py", line 528, in _value_for
[task 2019-05-08T12:59:01.891Z] 12:59:01 INFO - return self._value_for_option(obj)
[task 2019-05-08T12:59:01.891Z] 12:59:01 INFO - File "/builds/worker/workspace/build/src/python/mozbuild/mozbuild/util.py", line 947, in method_call
[task 2019-05-08T12:59:01.891Z] 12:59:01 INFO - cache[args] = self.func(instance, *args)
[task 2019-05-08T12:59:01.891Z] 12:59:01 INFO - File "/builds/worker/workspace/build/src/python/mozbuild/mozbuild/configure/init.py", line 591, in _value_for_option
[task 2019-05-08T12:59:01.891Z] 12:59:01 INFO - % option_string.split('=', 1)[0])
[task 2019-05-08T12:59:01.891Z] 12:59:01 INFO - mozbuild.configure.options.InvalidOptionError: --enable-profile-use is not available in this configuration
[task 2019-05-08T12:59:01.927Z] 12:59:01 INFO - *** Fix above errors and then restart with
[task 2019-05-08T12:59:01.927Z] 12:59:01 INFO - "./mach build"
[task 2019-05-08T12:59:01.927Z] 12:59:01 INFO - client.mk:111: recipe for target 'configure' failed
[task 2019-05-08T12:59:01.927Z] 12:59:01 INFO - make: *** [configure] Error 1

The above is from trying to run a Raptor profiling job based on an artifact build on Linux64. Other platforms like Windows worked fine.

Chris, would you mind having a look? It seems to be artifact build related. Thanks

Flags: needinfo?(cmanchester)

I think this is perma-fail for linux64-shippable builds on try with --artifact.

Yes, it is indeed. Marking as such.

Summary: Intermittent mozbuild.configure.options.InvalidOptionError: --enable-profile-use is not available in this configuration → Perma mozbuild.configure.options.InvalidOptionError: --enable-profile-use is not available in this configuration

Sorry for the delay, I believe the changes in bug 1553065 will fix this.

Flags: needinfo?(cmanchester)

(In reply to Chris Manchester (:chmanchester) from comment #8)

Sorry for the delay, I believe the changes in bug 1553065 will fix this.

Lets see. I pushed a new try build with the fix of bug 1553065 included:

https://treeherder.mozilla.org/#/jobs?repo=try&revision=8d1b55447b1e8ed0c08d8a01e4d4094212cdb888

It indeed looks to be fixed now. Thanks!

Assignee: nobody → mshal
Status: NEW → RESOLVED
Closed: 5 years ago
Depends on: 1553065
Resolution: --- → FIXED
Target Milestone: --- → mozilla69
You need to log in before you can comment on or make changes to this bug.