Closed Bug 486123 Opened 15 years ago Closed 14 years ago

try server talos should show crash stacks

Categories

(Release Engineering :: General, defect, P5)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dbaron, Unassigned)

References

Details

(Whiteboard: [talos][tryserver])

This is a followup to bug 458903 / bug 480577, but for try server.  (The unit test analog lives in bug 483111.)

Currently we don't get crash stacks from try server talos like we do from production talos.  This means if somebody submits a patch to try server talos and a crash results, they don't get much useful information.  (And, given that they may not have access to the pageset, they may not have a way to debug the problem.)

When a talos run on the try server crashes, it should have a stack like mozilla-central talos does.
The example that prompted this, for what it's worth, was a question from hsivonen about how to debug the problem in http://tinderbox.mozilla.org/showlog.cgi?log=MozillaTry/1238416440.1238424756.7292.gz&fulltext=1
catlee - do you want to take a look at this?
Assignee: nobody → catlee
Yes, Henri is blocked by not being able to see what/where/why his HTML5 parser changes crash on the try server, and is unable to reproduce locally. It'd be immensely helpful to get crash stacks here ASAP.
Thank you for filing this.

(Aside: The local crash from bug 482690 is back and apparently never went away--only changed URLs of occurrence, so the talos crash is I'm seeing likely to be it.)
Assignee: catlee → nobody
Component: Release Engineering: Talos → Release Engineering
Assignee: nobody → catlee
Assignee: catlee → nobody
Assignee: nobody → catlee
Assignee: catlee → nobody
Filed bug 497380 which blocks this one.  Futuring until that bug is able to be
taken on by someone.
Component: Release Engineering → Release Engineering: Future
No longer blocks: html5-parsing-land
Mass move of bugs from Release Engineering:Future -> Release Engineering. See
http://coop.deadsquid.com/2010/02/kiss-the-future-goodbye/ for more details.
Component: Release Engineering: Future → Release Engineering
Priority: -- → P3
Whiteboard: [talos]
Depends on: 520227
Priority: P3 → P5
Whiteboard: [talos] → [talos][tryserver]
got this for free when try-as-branch went live and started posting to talos-r3 just like production code.  closing.
Status: NEW → RESOLVED
Closed: 14 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.