Closed
Bug 1680786
Opened 4 years ago
Closed 4 years ago
Update FOG's rusttests docs for some common misconceptions
Categories
(Toolkit :: Telemetry, task, P3)
Toolkit
Telemetry
Tracking
()
RESOLVED
FIXED
90 Branch
Tracking | Status | |
---|---|---|
firefox90 | --- | fixed |
People
(Reporter: chutten, Assigned: chutten)
Details
(Whiteboard: [telemetry:fog:m?])
Attachments
(1 file)
In the investigation of a test failure, I stubbed my toes on a few things.
- Our tests that expect a panic do still print their panicking stack trace to stdout. If that test also fails, you'll see that stack trace and might suspect that's the culprit. It isn't.
- If a test fails explosively it'll poison the test lock, causing subsequent tests in the same run to fail. They can be safely ignored.
It'd be nice to add these to the test docs so we don't all have to rediscover these again later.
Assignee | ||
Comment 1•4 years ago
|
||
Updated•4 years ago
|
Assignee: nobody → chutten
Status: NEW → ASSIGNED
Pushed by chutten@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/529eb30c34e4
Clarify a couple things in FOG's rusttests docs r=janerik DONTBUILD
Comment 3•4 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox90:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 90 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•