Closed Bug 641986 Opened 15 years ago Closed 15 years ago

Hide NS_ERROR_FILE_NOT_FOUND failure message if log file cannot be found

Categories

(Mozilla QA Graveyard :: Mozmill Crowd Extension, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: aaronmt, Assigned: whimboo)

References

Details

Attachments

(2 files)

On start of a test-run during the init stage, the following error is produced. Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIFileInputStream.init] See screenshot
No longer depends on: 641897
Blocks: 641897
This was triggered during endurance_testrun's when setup was expecting a --screenshot-path which isnt available.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
I'm going to double check to confirm tomorrow, I'll reopen if I was wrong, but so far it's the case.
As said on IRC yesterday I will fix this message even we can't tell the user why we failed exactly.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Assignee: nobody → hskupin
Status: REOPENED → ASSIGNED
Keywords: regression
Summary: NS_ERROR_FILE_NOT_FOUND in init log file creation → Hide NS_ERROR_FILE_NOT_FOUND failure message if log file cannot be found
Attached patch Patch v1 — — Splinter Review
This patch makes sure that we delete the formerly log file and don't throw a failure message when it cannot be found after a testrun. That only happens when the testrun fails, i.e. run the add-ons testrun without trusted add-ons checked.
Attachment #519890 - Flags: review?(aaron.train)
Comment on attachment 519890 [details] [diff] [review] Patch v1 Looks fine, thanks
Attachment #519890 - Flags: review?(aaron.train) → review+
Status: ASSIGNED → RESOLVED
Closed: 15 years ago → 15 years ago
Hardware: x86 → All
Resolution: --- → FIXED
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: