Open
Bug 1528929
Opened 6 years ago
Updated 3 years ago
Running `artifact clear-cache` after `clobber` fails with config.status not available
Categories
(Firefox Build System :: General, defect, P3)
Firefox Build System
General
Tracking
(Not tracked)
NEW
People
(Reporter: jdescottes, Unassigned)
Details
(Keywords: in-triage)
STRs:
- enable artifact builds
- ./mach build
- ./mach clobber
- ./mach artifact clear-cache
Typically there was an issue while downloading the artifact in the build, and the idea was to cleanup the environment by running both clobber and removing the downloaded artifacts.
But artifact clear-cache
failed with:
Error running mach:
['artifact', 'clear-cache']
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 should consider filing a bug for this issue.
If filing a bug, please include the full output of mach, including this error
message.
The details of the failure are as follows:
BuildEnvironmentNotFoundException: config.status not available. Run configure.
File "/Users/jdescottes/Development/hg/fx-team/python/mozbuild/mozbuild/mach_commands.py", line 1281, in artifact_clear_cache
artifacts = self._make_artifacts(tree=tree, job=job)
File "/Users/jdescottes/Development/hg/fx-team/python/mozbuild/mozbuild/mach_commands.py", line 1247, in _make_artifacts
if conditions.is_hg(self):
File "/Users/jdescottes/Development/hg/fx-team/python/mozbuild/mozbuild/base.py", line 933, in is_hg
return getattr(cls, 'substs', {}).get('VCS_CHECKOUT_TYPE') == 'hg'
File "/Users/jdescottes/Development/hg/fx-team/python/mozbuild/mozbuild/base.py", line 302, in substs
return self.config_environment.substs
File "/Users/jdescottes/Development/hg/fx-team/python/mozbuild/mozbuild/base.py", line 285, in config_environment
raise BuildEnvironmentNotFoundException('config.status not available. Run configure.')
Since clobber
is not clearing artifact caches, in theory it should not prevent from clearing those caches?
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•