Closed Bug 406232 Opened 17 years ago Closed 17 years ago

crash reporter on bl-bldlnx03 and bl-bldxp01 should be disabled

Categories

(Release Engineering :: General, defect)

defect
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rhelmer, Unassigned)

Details

We had a service outage on bl-bldxp01 following a crash during tests because Breakpad came up and the build could not be removed (bug 406229).

We should make sure that test-only-tinderbox mode disables crash reporting (these are hourly builds so there are no symbols on the server anyway, no need to submit the results).
turns out bl-bldlnx03 has this problem, too, and it is most likely the cause of the perf regression we're seeing :(
OS: Windows XP → All
Hardware: PC → All
Summary: crash reporter on winxp perf box should be disabled → crash reporter on bl-bldlnx03 and bl-bldxp01 should be disabled
Severity: normal → major
It works fine, just someone (ie moi) forgot to do the perf boxes when they did all the other trunk machines. You're linking to the nightly tbox config, perf boxes are on the test_perf branch.

Checking in linux/tinder-config.pl;
/cvsroot/mozilla/tools/tinderbox-configs/firefox/linux/tinder-config.pl,v  <--  tinder-config.pl
new revision: 1.1.6.23; previous revision: 1.1.6.22
done
Checking in win32/tinder-config.pl;
/cvsroot/mozilla/tools/tinderbox-configs/firefox/win32/tinder-config.pl,v  <--  tinder-config.pl
new revision: 1.2.6.19; previous revision: 1.2.6.18
done
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.