Disable test_rocketbar_add_collection_save_bookmark.py until server-side issue are fixed
RESOLVED
FIXED
Status
People
(Reporter: martijn.martijn, Assigned: martijn.martijn)
Tracking
Firefox Tracking Flags
(Not tracked)
Details
(URL)
Attachments
(1 attachment)
|
46 bytes,
text/x-github-pull-request
|
gmealer
:
review+
|
Details | Review | Splinter Review |
| Comment hidden (empty) |
|
||
Comment 1•4 years ago
|
||
Created attachment 8606343 [details] [review] [gaia] mwargers:1165370 > mozilla-b2g:master
|
(Assignee) | |
Comment 2•4 years ago
|
||
Comment on attachment 8606343 [details] [review] [gaia] mwargers:1165370 > mozilla-b2g:master I don't know actually, if it's expected = random, if you expect sometimes the test to fail and sometimes not. Geo, do you perhaps know, where this is explained?
Attachment #8606343 -
Flags: review?(gmealer)
|
|
(Assignee) | |
Updated•4 years ago
|
Summary: Xfail test_rocketbar_add_collection_save_bookmark.py until server-side issue are fixed → Disable test_rocketbar_add_collection_save_bookmark.py until server-side issue are fixed
|
|
(Assignee) | |
Comment 3•4 years ago
|
||
Ok, it turns out there is no disabled = random, we should just disable this test.
Comment on attachment 8606343 [details] [review] [gaia] mwargers:1165370 > mozilla-b2g:master Looks fine, though I have been putting the root bug in the manifest, not the bug for actually disabling the test. So in your case I'd have done: disabled = Bug 1162112 - test_rocketbar_add_collection_save_bookmark.py: TimeoutException: TimeoutException: Timed out after 30.1 seconds (I removed the quotes because they might mess with manifest format). That said, it's not a big deal either way. Whether or not you decide to change the disabled reason, you don't need a re-review.
Attachment #8606343 -
Flags: review?(gmealer) → review+
|
|
(Assignee) | |
Comment 5•4 years ago
|
||
Ok, I changed it. https://github.com/mozilla-b2g/gaia/commit/c2b1db33acfb43ccf3e5023569dce96f2cf901f7
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.