Closed
Bug 1795168
Opened 2 years ago
Closed 2 years ago
Running `mach cargo check` on a clobbered tree fails
Categories
(Firefox Build System :: General, defect)
Firefox Build System
General
Tracking
(firefox108 fixed)
RESOLVED
FIXED
108 Branch
Tracking | Status | |
---|---|---|
firefox108 | --- | fixed |
People
(Reporter: glandium, Assigned: glandium)
Details
Attachments
(1 file)
Error running mach:
['cargo', 'check']
The error occurred in code that was called by the mach command. This is either
a bug in the called code itself or in the way that mach is calling it.
You can invoke |./mach busted| to check if this issue is already on file. If it
isn't, please use |./mach busted file cargo| to report it. If |./mach busted| is
misbehaving, you can also inspect the dependencies of bug 1543241.
If filing a bug, please include the full output of mach, including this error
message.
The details of the failure are as follows:
mozbuild.base.BuildEnvironmentNotFoundException: config.status not available. Run configure.
File "/tmp/gecko/python/mozbuild/mozbuild/mach_commands.py", line 182, in check
ret = command_context._run_make(
File "/tmp/gecko/python/mozbuild/mozbuild/base.py", line 723, in _run_make
args = [self.substs["GMAKE"]]
File "/tmp/gecko/python/mozbuild/mozbuild/base.py", line 396, in substs
return self.config_environment.substs
File "/tmp/gecko/python/mozbuild/mozbuild/base.py", line 372, in config_environment
raise BuildEnvironmentNotFoundException(
Assignee | ||
Comment 1•2 years ago
|
||
Also change the default value for --jobs to 0 instead of 1, because
make -j1
doesn't initialize a jobserver, so cargo uses all cores,
which is a fine default, but now that we may also invoke the rest of
the build system, and because make -j1
for that is slow, we instead
use 0 as the default (which means auto-detect).
Pushed by mh@glandium.org: https://hg.mozilla.org/integration/autoland/rev/3a5c6fdd31b4 Make `mach cargo check` initialize enough of the build for its own purpose . r=firefox-build-system-reviewers,nalexander
Comment 3•2 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox108:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 108 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•