Closed
Bug 1724219
Opened 4 years ago
Closed 4 years ago
[browsertime] make browsertime command warning less scary
Categories
(Testing :: Performance, defect, P2)
Tracking
(firefox97 fixed)
RESOLVED
FIXED
97 Branch
| Tracking | Status | |
|---|---|---|
| firefox97 | --- | fixed |
People
(Reporter: kimberlythegeek, Assigned: kimberlythegeek)
References
Details
(Whiteboard: [fxp][developer-experience])
Attachments
(1 file)
Browsertime is configured to display this warning when it is run, advising users to run browsertime raptor instead:
0:01.75 [WARNING] This tool is UNSUPPORTED by the perftest team and it is NOT recommended to use for performance testing. Instead, if you are looking to perform performance tests on your patch, use `./mach raptor --browsertime`.
Add an exception so that this warning is not displayed when run with the --setup flag
| Assignee | ||
Updated•4 years ago
|
Priority: -- → P3
Comment 1•4 years ago
|
||
There may be other commands we want to allow, such as --update-upstream-url. Perhaps we could simply move this message into the else block of this code: https://searchfox.org/mozilla-central/rev/00977c4e37865a92f1c15572ae4aea90e934b25b/tools/browsertime/mach_commands.py#660-666
Updated•4 years ago
|
Severity: -- → S3
| Assignee | ||
Updated•4 years ago
|
Summary: [browsertime] Add exception for usage warning when running --setup → [browsertime] make browsertime command warning less scary
| Assignee | ||
Comment 2•4 years ago
|
||
Updated•4 years ago
|
Assignee: nobody → ksereduck
Status: NEW → ASSIGNED
Pushed by ksereduck@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/97a426816756
make browsertime command warning less scary r=perftest-reviewers,AlexandruIonescu
Comment 4•4 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox97:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 97 Branch
Updated•2 years ago
|
Whiteboard: [fxp]
Updated•2 months ago
|
Priority: P3 → P2
Updated•2 months ago
|
Whiteboard: [fxp] → [fxp][developer-experience]
You need to log in
before you can comment on or make changes to this bug.
Description
•