Closed Bug 1732999 Opened 3 years ago Closed 3 years ago

MOZ_BUILDID_MATCH_DONTSEND crash should call NoteIntentionalCrash()

Categories

(Core :: IPC, defect)

defect

Tracking

()

RESOLVED FIXED
94 Branch
Tracking Status
firefox-esr78 --- unaffected
firefox-esr91 --- fixed
firefox92 --- wontfix
firefox93 --- wontfix
firefox94 --- fixed

People

(Reporter: mccr8, Assigned: gerard-majax)

References

(Regression)

Details

(Keywords: regression)

Attachments

(1 file)

Bug 1651133 looks like it added an intentional crash for the purposes of the test. However, this is bad because the leak checker expects that any process that started the leak checker will produce a leak log. The fix here is easy, though: just call NoteIntentionalCrash() right before you crash. That will add the right annotation into the leak log.

(This should make the test orange, but for some reason it seems not to, so bug 1560096 only gets flagged when the test turns orange for another reason?)

Do you have time to fix this soon? Thanks.

Flags: needinfo?(lissyx+mozillians)
Type: task → defect
Assignee: nobody → lissyx+mozillians
Flags: needinfo?(lissyx+mozillians)

Andrew, there has been no problem with this code reported so far, why all of a sudden is it failing ? Try on the suggested change is even worse: https://treeherder.mozilla.org/jobs?repo=try&revision=0a1e991f57a8fc573f54c71854fa988c5d7db649

Could you please link me to a sample of the actual problem ?

Flags: needinfo?(continuation)

Actually, I got tricked by our infra ... Requesting fuzzy run on direct files triggered their run on opt builds where it is not supported ...

Flags: needinfo?(continuation)
Pushed by alissy@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/d9fe777ae495
Annotate intentional crash when testing buildid mismatch r=mccr8

(In reply to Alexandre LISSY :gerard-majax from comment #4)

Andrew, there has been no problem with this code reported so far, why all of a sudden is it failing ?

I think this is always failing, and has probably always been failing since it landed. There's some issue with TreeHerder that means these failures don't turn the tree orange. For instance, this looks like a recent instance of the build id test failing to leave a leak log: https://treeherder.mozilla.org/logviewer?job_id=353060810&repo=mozilla-central&lineNumber=60827

There is an error, but the job still shows up as green. What can happen is that some other failure happens in the same run, which turns the job orange, and then the sherriff flags this error instead of the one that actually turned it orange.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 94 Branch

Comment on attachment 9243420 [details]
Bug 1732999 - Annotate intentional crash when testing buildid mismatch r?mccr8!

ESR Uplift Approval Request

  • If this is not a sec:{high,crit} bug, please state case for ESR consideration: This fixes an intermittent failure.
  • User impact if declined: none
  • Fix Landed on Version: 94
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): This code is MOZ_DEBUG-only and only affects a codepath used for testing.
  • String or UUID changes made by this patch: none
Attachment #9243420 - Flags: approval-mozilla-esr91?

Comment on attachment 9243420 [details]
Bug 1732999 - Annotate intentional crash when testing buildid mismatch r?mccr8!

Approved for 91.3esr.

Attachment #9243420 - Flags: approval-mozilla-esr91? → approval-mozilla-esr91+
Has Regression Range: --- → yes
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: