Closed
Bug 1850905
Opened 3 years ago
Closed 2 years ago
Link Raptor unit tests to mozperftest locally
Categories
(Testing :: Raptor, task, P2)
Testing
Raptor
Tracking
(firefox128 fixed)
RESOLVED
FIXED
128 Branch
| Tracking | Status | |
|---|---|---|
| firefox128 | --- | fixed |
People
(Reporter: afinder, Assigned: afinder)
References
(Depends on 2 open bugs, Blocks 2 open bugs)
Details
(Whiteboard: [fxp][operational][softvision-kpi])
Attachments
(1 external file)
No description provided.
|
||
Updated•3 years ago
|
|
Assignee | |
Comment 1•2 years ago
|
||
I tried changing the code that runs the mozperftest tests via the pytest subprocess to also include the path to the raptor tests, but it doesn't seem to be as straightforward. I managed to include the paths to the following 3 modules (although by omitting the "coverage" argument) without any errors: "test_cmdline.py", "test_print_tests.py", "test_playback.py". All of the other raptor modules are failing. Currently looking into debugging each of the failing modules individually.
|
|
Assignee | |
Comment 2•2 years ago
|
||
Depends on D210935
Pushed by afinder@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/e4fc2afefffc
Link Raptor unit tests to mozperftest locally r=perftest-reviewers,sparky
|
||
Comment 4•2 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox128:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 128 Branch
|
||
Updated•8 months ago
|
Whiteboard: [fxp] → [fxp][operational][softvision-kpi]
You need to log in
before you can comment on or make changes to this bug.
Description
•