Closed
Bug 1870536
Opened 1 year ago
Closed 1 year ago
Running ./mach xpcshell-test is broken (failed to find manifest)
Categories
(Testing :: XPCShell Harness, defect)
Testing
XPCShell Harness
Tracking
(firefox123 fixed)
RESOLVED
FIXED
123 Branch
Tracking | Status | |
---|---|---|
firefox123 | --- | fixed |
People
(Reporter: standard8, Assigned: jmaher)
References
(Blocks 2 open bugs)
Details
Attachments
(1 file)
If I run something like one of the two following commands, the tests fails to run:
./mach xpcshell-test toolkit/components/search/tests/xpcshell/test_async.js
./mach xpcshell-test toolkit/components/search/tests/xpcshell/
If I run them with simply ./mach test
then they work.
The failure is:
0:00.20 ERROR Failed to find manifest at /Users/mark/dev/gecko/objdir-ff-opt/_tests/xpcshell/xpcshell.ini/xpcshell.ini; use --manifest to set path explicitly.
I suspect this is a regression from some of the toml changes.
Flags: needinfo?(jmaher)
Reporter | ||
Updated•1 year ago
|
Blocks: mach-busted
Assignee | ||
Comment 1•1 year ago
|
||
thanks for this, I have a patch upcoming that should fix this. probably a few more edge cases related to toml migration;
Flags: needinfo?(jmaher)
Assignee | ||
Comment 2•1 year ago
|
||
Updated•1 year ago
|
Assignee: nobody → jmaher
Status: NEW → ASSIGNED
Pushed by jmaher@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/c369d7521de5
fix remaining references to .ini in xpcshell. r=gbrown
Comment 4•1 year ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox123:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 123 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•