Closed
Bug 740773
Opened 14 years ago
Closed 14 years ago
No error messages when sending report to a remote host fails
Categories
(Testing Graveyard :: Mozmill, defect)
Testing Graveyard
Mozmill
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: automatedtester, Assigned: davehunt)
Details
(Whiteboard: [mozmill-1.5.10+][mozmill-2.0+])
Attachments
(3 files, 1 obsolete file)
After working on bug 703789 it was noticed that Mozmill does not report error messages properly if Mozmill Dashboard blocks the data
| Reporter | ||
Comment 1•14 years ago
|
||
Pointer to Github pull-request
| Reporter | ||
Updated•14 years ago
|
Attachment #610860 -
Flags: review?(jhammel)
Comment 2•14 years ago
|
||
Clint, it would be great if this could be approved for Mozmill 1.5.10. Things like that are annoying when we have to investigate failures. Now with the validation function in place it's even unclear to the user if something fails.
Assignee: nobody → dburns
Status: NEW → ASSIGNED
Summary: Error messages from Mozmill Dashboard are not reported in Mozmill → No error messages when sending report to a remote host fails
Whiteboard: [mozmill-1.5.9?][mozmill-2.0?]
Comment 3•14 years ago
|
||
Comment on attachment 610860 [details]
Pointer to Github pull request: https://github.com/mozautomation/mozmill/pull/12
wfm; the pull request is to master but we will probably want this on 2.0 and probably 1.5
Attachment #610860 -
Flags: review?(jhammel) → review+
Comment 4•14 years ago
|
||
Given that no-one checked my comment on the pull request (which you should do before you give review here) I will copy it into the bug:
Wow, what a silly mistake. David, can you please make so that we only show the data['reason'] value here? The others we really don't need.
Also do we still show the host we send the report to? If not we should print the error reason in a new line.
So before we check this into older branches please get those comments addressed first.
| Assignee | ||
Comment 5•14 years ago
|
||
I've made a suggestion on the Github pull request (repeated below, original here: https://github.com/mozautomation/mozmill/pull/12#issuecomment-4953820
), which addresses Henrik's comment:
If instead we use this:
# Check if the report has been created
if not 'ok' in data:
raise Exception(data['reason'])
We get the failure as:
Sending results to 'http://mozmill-crowd.blargon7.com/db/' failed (This document requires the field report_version).
Did you want me to put together a new pull request?
Updated•14 years ago
|
Whiteboard: [mozmill-1.5.9?][mozmill-2.0?] → [mozmill-1.5.10?][mozmill-2.0?]
(In reply to Dave Hunt (:davehunt) from comment #5)
> I've made a suggestion on the Github pull request (repeated below, original
> here: https://github.com/mozautomation/mozmill/pull/12#issuecomment-4953820
> ), which addresses Henrik's comment:
>
> If instead we use this:
>
> # Check if the report has been created
> if not 'ok' in data:
> raise Exception(data['reason'])
>
> We get the failure as:
>
> Sending results to 'http://mozmill-crowd.blargon7.com/db/' failed (This
> document requires the field report_version).
>
> Did you want me to put together a new pull request?
Yes, let's do that. Can you make a new pull request.
Updated•14 years ago
|
Assignee: dburns → dave.hunt
Whiteboard: [mozmill-1.5.10?][mozmill-2.0?] → [mozmill-1.5.10+][mozmill-2.0+]
| Assignee | ||
Comment 7•14 years ago
|
||
New pull request is up: https://github.com/mozautomation/mozmill/pull/13
| Assignee | ||
Comment 8•14 years ago
|
||
Pointer to Github pull-request
| Assignee | ||
Comment 9•14 years ago
|
||
Pointer to Github pull-request
| Assignee | ||
Updated•14 years ago
|
Attachment #613746 -
Attachment is obsolete: true
| Assignee | ||
Updated•14 years ago
|
Attachment #613745 -
Flags: review?(ctalbert)
| Assignee | ||
Updated•14 years ago
|
Attachment #610860 -
Attachment is obsolete: true
Comment 10•14 years ago
|
||
Comment on attachment 613745 [details]
Pointer to Github pull request: https://github.com/mozautomation/mozmill/pull/13
looks great
Attachment #613745 -
Flags: review?(ctalbert) → review+
Comment 11•14 years ago
|
||
Comment on attachment 610860 [details]
Pointer to Github pull request: https://github.com/mozautomation/mozmill/pull/12
This attachment is not obsolete. It has been checked-in.
Attachment #610860 -
Attachment is obsolete: false
Comment 12•14 years ago
|
||
Landed with the merge on master:
https://github.com/mozautomation/mozmill/commit/a14344b369bd1fe7c6c8fc30c67290e7b2c5945a
Also I have cherry-picked both patches and landed those on hotfix-2.0:
https://github.com/mozautomation/mozmill/compare/61af56a...ae43517
Dave, can you please submit a combined patch for the hotfix-1.5 branch?
| Assignee | ||
Comment 13•14 years ago
|
||
Pointer to Github pull-request
| Assignee | ||
Comment 14•14 years ago
|
||
Comment on attachment 613926 [details]
Pointer to Github pull request: https://github.com/mozautomation/mozmill/pull/15
Patch for hotfix-1.5 branch.
Attachment #613926 -
Flags: review?(hskupin)
Comment 15•14 years ago
|
||
Comment on attachment 613926 [details]
Pointer to Github pull request: https://github.com/mozautomation/mozmill/pull/15
Looks good. Landed on hotfix-1.5:
https://github.com/mozautomation/mozmill/commit/b2f47fb26c203d842f35d89fe2ef6731608e3185
Attachment #613926 -
Flags: review?(hskupin) → review+
Comment 16•14 years ago
|
||
So we are done here. Thanks Dave!
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•9 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•