Closed
Bug 640129
Opened 13 years ago
Closed 13 years ago
Report type contains NotImplementedError as value
Categories
(Testing Graveyard :: Mozmill, defect)
Testing Graveyard
Mozmill
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: whimboo, Assigned: k0scist)
References
Details
(Whiteboard: [mozmill-2.0+])
Attachments
(2 files)
1.08 KB,
patch
|
harth
:
review+
|
Details | Diff | Splinter Review |
618 bytes,
patch
|
ahal
:
review+
|
Details | Diff | Splinter Review |
With the latest changeset on master the report_type entry in the report written out by Mozmill contains the following value: "report_type": "NotImplementedError" Looks like something broke in the last couple of weeks probably due to the refactoring.
Reporter | ||
Updated•13 years ago
|
Whiteboard: [mozmill-2.0?]
Assignee | ||
Updated•13 years ago
|
Assignee: nobody → jhammel
OS: Mac OS X → All
Hardware: x86 → All
Assignee | ||
Updated•13 years ago
|
Whiteboard: [mozmill-2.0?] → [mozmill-2.0+]
Assignee | ||
Comment 1•13 years ago
|
||
Attachment #519558 -
Flags: review?(fayearthur+bugs)
Comment 2•13 years ago
|
||
Comment on attachment 519558 [details] [diff] [review] remove report_type entirely, deprecated no more MozmillRestart, so this make sense.
Attachment #519558 -
Flags: review?(fayearthur+bugs) → review+
Assignee | ||
Comment 3•13 years ago
|
||
yeah; when we gained the ability to run restart and non-restart tests in the same (python) process, report_type no longer made since, which is when I returned the string NotImplementedError (note: string, not the exception of the same name). I forgot the reason -- probably because a quick consensus could not be reached on what (if anything). This is just cleanup from that which makes more sense as the line between restart and non-restart tests becomes increasingly blurred.
Assignee | ||
Comment 4•13 years ago
|
||
pushed to master: https://github.com/mozautomation/mozmill/commit/b19629cb9725d454ddc5c48e5e0f22bc574d77d7
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 5•13 years ago
|
||
That change will need a fix in our dashboard code, so we don't fail on a non-existing report_type field. Otherwise I'm fine with the removal.
Assignee | ||
Comment 6•13 years ago
|
||
If it helps to return a stub value, we can, but there's no longer a distinction between restart and non-restart runs as.
Reporter | ||
Comment 7•13 years ago
|
||
If you could simply include "mozmill-test" as report type it would be great.
Assignee | ||
Comment 8•13 years ago
|
||
adds in a dummy report type
Attachment #519726 -
Flags: review?(ahalberstadt)
Assignee | ||
Comment 9•13 years ago
|
||
(In reply to comment #7) > If you could simply include "mozmill-test" as report type it would be great. see comment #8
Comment 10•13 years ago
|
||
Comment on attachment 519726 [details] [diff] [review] include a (dummy) report type r+
Attachment #519726 -
Flags: review?(ahalberstadt) → review+
Assignee | ||
Comment 11•13 years ago
|
||
(In reply to comment #9) > (In reply to comment #7) > > If you could simply include "mozmill-test" as report type it would be great. > > see comment #8 pushed to master: https://github.com/mozautomation/mozmill/commit/81e14ef3f80f1097ab763ec36ad1ee480232216e
Updated•8 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•