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

NEW
Unassigned

Status

P3
normal
5 years ago
8 months ago

People

(Reporter: gps, Unassigned)

Tracking

Trunk

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

5 years ago
+++ 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.
(Reporter)

Comment 1

5 years ago
Created attachment 8356858 [details] [diff] [review]
Report source manifest during xpcshell test execution

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
(Reporter)

Updated

5 years ago
Assignee: nobody → gps
Status: NEW → ASSIGNED

Updated

5 years ago
Priority: -- → P3
(Reporter)

Updated

5 years ago
Assignee: gps → nobody
Status: ASSIGNED → NEW

Updated

8 months ago
Product: Core → Firefox Build System
You need to log in before you can comment on or make changes to this bug.