Closed Bug 840485 Opened 13 years ago Closed 13 years ago

Test failure "The crash reporter executable is present - got 'false'" in /testInstallation/testBreakpadInstalled.js

Categories

(Mozilla QA Graveyard :: Mozmill Tests, defect, P2)

defect

Tracking

(firefox20 fixed, firefox21 fixed, firefox22 fixed)

RESOLVED FIXED
Tracking Status
firefox20 --- fixed
firefox21 --- fixed
firefox22 --- fixed

People

(Reporter: AndreeaMatei, Assigned: AndreeaMatei)

References

()

Details

(Whiteboard: [mozmill-test-failure] s=130218 u=failure c=installation p=1)

Attachments

(2 files, 1 obsolete file)

Started today on all OS X versions with Nightly fr locale.
Whiteboard: [mozmill-test-failure]
Attached patch skip patch — — Splinter Review
Disabling the test until we find the regression and fix it.
Assignee: nobody → andreea.matei
Status: NEW → ASSIGNED
Attachment #713083 - Flags: review?(dave.hunt)
OS: Mac OS X → All
Hardware: x86 → All
I'm able to replicate this locally on Mac OS X 10.8.2 and Nightly with build ID: 20130212031120
Comment on attachment 713083 [details] [diff] [review] skip patch Review of attachment 713083 [details] [diff] [review]: ----------------------------------------------------------------- Landed as: http://hg.mozilla.org/qa/mozmill-tests/rev/f0cb8723616a (default)
Attachment #713083 - Flags: review?(dave.hunt)
Attachment #713083 - Flags: review+
Attachment #713083 - Flags: checkin+
Last good build: 2013-02-11 First bad build: 2013-02-12 Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?startdate=2013-02-11&enddate=2013-02-12
This may be another fallout from bug 755724... Could you try to reduce the regression range and if this is a Firefox regression please raise a bug today.
That's exactly what I am doing :) We should have that figured out today.
Whiteboard: [mozmill-test-failure] → [mozmill-test-failure] s=130218 u=failure c=installation p=1
This is a failure in our test and not in Firefox. So lets get this fixed.
Priority: -- → P2
Attached patch fix path (obsolete) — — Splinter Review
This failure was caused by changes in this changeset: http://hg.mozilla.org/mozilla-central/rev/784b9beebe90 It is only on default, where path was changed from Nightly/firefox/ to Nightly/firefox/browser. 'browser' is a new subdirectory, 'chrome' folder was moved in this one. The application crashreporter is in the first location, in 'browser' I found file crashreporter-override (which in Aurora is still on the main folder). I edited some style guide issues as well. Reports: OS X: http://mozmill-crowd.blargon7.com/#/functional/report/f36358d058daf73ddbf78150162deef4 Linux: http://mozmill-crowd.blargon7.com/#/functional/report/f36358d058daf73ddbf78150162e83d8 Win: http://mozmill-crowd.blargon7.com/#/functional/report/f36358d058daf73ddbf78150162e91ea
Attachment #715458 - Flags: review?(hskupin)
Attachment #715458 - Flags: review?(dave.hunt)
Comment on attachment 715458 [details] [diff] [review] fix path Review of attachment 715458 [details] [diff] [review]: ----------------------------------------------------------------- ::: tests/functional/testInstallation/testBreakpadInstalled.js @@ +24,1 @@ > controller = mozmill.getBrowserController(); nit: while we are on it, please set it to aModule.controller. @@ -49,5 @@ > "The Breakpad server URL is correct"); > } > - > -setupModule.__force_skip__ = "Bug 840485 - Test failure " + > - "'The crash reporter executable is present - got 'false''"; Don't forget to also update the manifest file.
Attachment #715458 - Flags: review?(hskupin)
Attachment #715458 - Flags: review?(dave.hunt)
Attachment #715458 - Flags: review-
Attached patch patch v1 — — Splinter Review
Sorry I missed that. Fixed now.
Attachment #715458 - Attachment is obsolete: true
Attachment #715489 - Flags: review?(hskupin)
Attachment #715489 - Flags: review?(dave.hunt)
Comment on attachment 715489 [details] [diff] [review] patch v1 Review of attachment 715489 [details] [diff] [review]: ----------------------------------------------------------------- http://hg.mozilla.org/qa/mozmill-tests/rev/0dd2dc62cc0e (default)
Attachment #715489 - Flags: review?(hskupin)
Attachment #715489 - Flags: review?(dave.hunt)
Attachment #715489 - Flags: review+
Attachment #715489 - Flags: checkin+
Applies and tests well on Aurora too.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
This was due to bug 869242, which Henrik solved now. Tests are passing after being retriggered.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Please stop reopening fixed bugs. That's really not helpful, especially when it was proven it fixed the problem. The new issue is totally different. You/we might want to find better summaries for bugs which explains about their nature to lessen such a confusion.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
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: