Closed Bug 854510 Opened 11 years ago Closed 11 years ago

UNEXPECTED-PASS: js/xpconnect/tests/chrome/test_bug503926.xul - Assertion count 0 is less than expected range 1-1 assertions.

Categories

(Core :: XPConnect, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla22

People

(Reporter: bholley, Assigned: bholley)

Details

Attachments

(1 file)

This has been going red on my local machine for several weeks now. I'm assuming the fact that it's not red on tinderbox means that it asserts there, so I guess this should be turned into a range. Patch coming up.
Comment on attachment 729100 [details] [diff] [review]
Convert expected assertion into a 0-1 range. v1

So something in your patch queue fixes it then? Great! Just don't forget to drop the annotation when you land whatever it is that did.
Attachment #729100 - Flags: review?(ryanvm) → review+
Though if that's the case, I'd prefer that you just land that patch with the fix and not land this one.
(In reply to Ryan VanderMeulen [:RyanVM] from comment #2)

> So something in your patch queue fixes it then? Great! Just don't forget to
> drop the annotation when you land whatever it is that did.

No. The test just doesn't assert when run locally. I don't even know what the assertion is.
For reference, the assertion was:

ASSERTION: Existing entry in StartupCache.: 'entry == nullptr', file ../../startupcache/StartupCache.cpp

https://hg.mozilla.org/integration/mozilla-inbound/rev/78d672df644f
https://hg.mozilla.org/mozilla-central/rev/78d672df644f
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla22
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: