Open
Bug 1978146
Opened 11 months ago
Updated 10 months ago
Gradle doesn't support multiple mozconfigs and multiple builds when running tests
Categories
(Firefox for Android :: Tooling, defect, P1)
Tracking
()
People
(Reporter: owlish, Assigned: owlish)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 obsolete file)
Steps to reproduce
- Build Fenix with a custom mozconfig like
MOZCONFIG=mySpecial.mozconfig ./mach build - Run tests on that build
MOZCONFIG=mySpecial.mozconfig ./mach gv-junit blabla, observe the correct object dir and build config being used by examining the logs and/or adding assertions to the test - No try running the tests with your regular mozconfig
./mach gv-junit blabla
Expected behavior
observe it now uses the object dir and build config for the regular mozconfig build
Actual behavior
observe it still uses the object dir and build config for the mySpecial.mozconfig build
Any additional information?
The issue could not be fixed by rebuilding, resetting the emulator, clobbering the build, bootstraping, restarting the emulator, etc.
Commenting out these lines helped fix the issue
| Assignee | ||
Updated•11 months ago
|
Assignee: nobody → bugzeeeeee
Severity: -- → S3
Priority: -- → P1
| Assignee | ||
Comment 1•11 months ago
|
||
Comment 2•11 months ago
|
||
Set release status flags based on info from the regressing bug 1924520
status-firefox140:
--- → affected
status-firefox141:
--- → affected
status-firefox142:
--- → affected
Updated•11 months ago
|
Comment 3•11 months ago
|
||
Set release status flags based on info from the regressing bug 1924520
status-firefox143:
--- → affected
Updated•11 months ago
|
Updated•11 months ago
|
Attachment #9501617 -
Attachment is obsolete: true
Updated•11 months ago
|
Updated•10 months ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•