Open Bug 957380 Opened 11 years ago Updated 3 years ago

xpcshell harness doesn't identify which manifest a test came from

Categories

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

defect

Tracking

(Not tracked)

People

(Reporter: gps, Unassigned)

References

Details

Attachments

(1 file)

+++ This bug was initially created as a clone of Bug #920849 +++ As reported in bug 920849, the xpcshell harness isn't clear about which manifest a test came from. Tests defined in a shared manifest (namely toolkit/mozapps/extensions/test/xpcshell/xpcshell-shared.ini) show up twice in output and people don't know if the packed or unpacked version failed. We should change the test runner output to capture which manifest the test came from. This *may* impact error strings and cause orange factor and other automated agents relying on string matching to get all fussy. We should proceed with caution.
This patch will change the output formatting to include the manifest file. I'm pretty some unit tests will fail. But local developers can use this to debug failures in the addon manager tests. https://tbpl.mozilla.org/?tree=Try&rev=20a7bfca7fb6
Assignee: nobody → gps
Status: NEW → ASSIGNED
Priority: -- → P3
Assignee: gps → nobody
Status: ASSIGNED → NEW
Product: Core → Firefox Build System
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: