Closed
Bug 1629502
Opened 4 years ago
Closed 4 years ago
Move -cranelift- raptor tests to tier 2
Categories
(Testing :: Raptor, task, P1)
Tracking
(firefox77 fixed)
RESOLVED
FIXED
mozilla77
Tracking | Status | |
---|---|---|
firefox77 | --- | fixed |
People
(Reporter: Bebe, Assigned: Bebe)
References
Details
Attachments
(1 file)
No description provided.
Assignee | ||
Comment 1•4 years ago
|
||
Updated•4 years ago
|
Summary: Move raptor-wasm-godot-cranelift-firefox to tire 2 → Move raptor-wasm-godot-cranelift-firefox to tier 2
Updated•4 years ago
|
Attachment #9140099 -
Attachment description: Bug 1629502 - Move raptor-wasm-godot-cranelift-firefox to tire 2 → Bug 1629502 - Move raptor-wasm-godot-cranelift-firefox to tier 2
Assignee | ||
Comment 2•4 years ago
|
||
Question from the code review:
Shouldn't this be applied to all the wasm-godot jobs? @bbouvier can help with that.
Flags: needinfo?(bbouvier)
Comment 3•4 years ago
|
||
Shouldn't this be applied to all the wasm-godot jobs? @bbouvier can help with that.
No, only the Cranelift ones. Just to make sure we're on the same page, the intent here is to move all the Cranelift benchmarks to tier 2, so that would be wasm-godot on Cranelift, and wasm-misc on Cranelift. So I think the patch needs a small update here.
Flags: needinfo?(bbouvier) → needinfo?(fstrugariu)
Assignee | ||
Updated•4 years ago
|
Flags: needinfo?(fstrugariu)
Summary: Move raptor-wasm-godot-cranelift-firefox to tier 2 → Move -cranelift- raptor tests to tier 2
Updated•4 years ago
|
Attachment #9140099 -
Attachment description: Bug 1629502 - Move raptor-wasm-godot-cranelift-firefox to tier 2 → Bug 1629502 - Move -cranelift- raptor tests to tier 2
Pushed by fstrugariu@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/f805ca6a339a Move -cranelift- raptor tests to tier 2 r=perftest-reviewers,AlexandruIonescu,whimboo
Comment 5•4 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox77:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla77
You need to log in
before you can comment on or make changes to this bug.
Description
•