Closed Bug 313050 Opened 19 years ago Closed 19 years ago

No talkbacks anymore in hourly zip builds

Categories

(Webtools Graveyard :: Tinderbox, defect)

x86
Windows XP
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: ria.klaassen, Assigned: chase)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b5) Gecko/20051019 Firefox/1.5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b5) Gecko/20051019 Firefox/1.5 I miss the talkbacks in hourly zip builds. In branch it was included in 1.8b5_2005101107 but not anymore in 1.8b5_2005101110. In trunk I saw the last talkback in 1.9a1_2005101104 but it was gone in 1.9a1_2005101121. Forgive me my ignorance if this is a policy. :) Reproducible: Always
It's not installed everywhere : only a small percentage of instalations get it by default, to prevent overload of the talkback server. You can force installation with the custom installation.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
So you can't use hourlies anymore for testing crashes unless you install them? Only the installer hourly builds are usable for testing?
Summary: No talkbacks anymore in hourlies → No talkbacks anymore in hourly zip builds
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Reopened because of possible misunderstanding.
It is a bit labour-intensive to copy & paste a talkback from an old build into the folder extensions of every build you want to try..
As far as I know, Talkback only works (produces stack traces with function names, etc) with nightlies, so it doesn't make sense to expect the Talkback client to be included with hourlies.
(In reply to comment #4) > It is a bit labour-intensive to copy & paste a talkback from an old build into > the folder extensions of every build you want to try.. It doesn't work this way. Talkback can't be transferred from one build to another, as the builds differ in symbol addresses. You'll get a talkback record, but it talks nonsense. Also a Talkback Report is useful only as long as the symbols are available at the talkback server. Crash with an older build, and you get a talkback record with offsets instead of sysmbols, no links to LXR. I don't think talkback is useful for hourly builds. Who long is an hourly build used? Until the next arrives. How long must the symbols be retained at the server? Imho it makes sense to have talkback in the nightlies. They are longer used, a day, or a week.
Assignee: nobody → chase
Component: General → Tinderbox Configuration
Product: Firefox → mozilla.org
QA Contact: general → ccooper
Version: unspecified → other
Due to resource limitations, we only package Talkback with nightlies. And as mentioned, copying over Talkback files to other builds is not a good idea. We are working on expanding our symbols space to keep symbols around for longer periods of time, but for now, we only have the capacity to hold about 10 days worth of symbols for nightlies...so please use those builds for crash testing. We hope to grow the days to 30, but even then we plan to only include Talkback with nightlies. Marking WONTFIX. Sorry...
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago19 years ago
Resolution: --- → WONTFIX
If they didn't work it is no loss. :)
Well, miracles still happen; they are back! :D
Ria: Keep in mind that any crashes you send in will be useless since we do not store symbols for the hourly builds on the Talkback processing server. :-( If you are able to reproduce a crash, it will be nice if you could try with a nightly so we get some good data. Thanks for the update.
OK. Any thoughts why they are included again (as this will generate a lot of useless information)?
Component: Tinderbox Configuration → Tinderbox
Product: mozilla.org → Webtools
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.