Closed
Bug 1365514
Opened 8 years ago
Closed 8 years ago
Bughunter should be better on identifying urls (and not just say its startup)
Categories
(Testing Graveyard :: Sisyphus, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: cbook, Unassigned)
References
Details
(Whiteboard: [fixed-by-bug-1365240])
Attachments
(1 file)
|
7.46 KB,
text/plain
|
Details |
For some reasons productions and bavarian bughunter db show a lot of startup crashes. Like
mozilla::dom::DocGroup::ValidateAccess nsDocument::BeginUpdate nsStyleLinkElement::DoUpdateStyleSheet nsStyleLinkElement::UpdateStyleSheetInternal mozilla::dom::HTMLStyleElement::UnbindFromTree
Assertion failure: !sRunningDispatcher || mAccessValid
Windows NT 10.0 x86_64 x86_64 firefox nightly debug startup
2017-05-15 11:11:15 EXCEPTION_BREAKPOINT 0x7ff9d481d960
view content none
view
that "startup" is not really startup its:
https://online.citi.com/US/login.do?JFP_TOKEN=2017TCBC: EXIT STATUS: TIMED OUT (179.995342016 seconds) etc
it seems related to
54 _err /mozilla/builds/hg.mozilla.org/sisyphus/bin/library.sh
128 main tests/mozilla.org/top-sites/test.sh
From the log it seems the site was loaded and bughunter found issues but was not able to notify us with the real url.
The Problem might be that we miss crashes/issues because of this. In the case above with the assertion i was able to reproduce and will file now
Comment 2•8 years ago
|
||
Pretty sure this is fixed by bug 1365240. Prior to that Spider wasn't being installed so the log didn't contain the information about the url that was being tested. Lacking the url in the log, the system assigned startup. I see about 150 "startup" crashes yesterday and none today which leads me to thing this is the case.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(bob)
Resolution: --- → FIXED
See Also: → 1365240
Whiteboard: [fixed-by-bug-1365240]
Updated•6 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•