297555 - Talkback build date/time is incorrect

Status: RESOLVED DUPLICATE of bug 353747

(Firefox Build System :: General, defect)

Description

[Radek 'sysKin' Czyz]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050610 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050610 Firefox/1.0+

In both Beast and Pacifica builds, the build time/date in talkback's master.ini
file doesn't correspond to the actual buildID.
In Beast, the ID is fixed at 2005051906. In Pacifica, a 13/06/2005 is dated
2005061219 instead. At least with Beast this is quite wrong.

Reproducible: Always

Steps to Reproduce:
1. Crash with 06/10 Beast build
2. Check your talkback (for example TB6597055E)

Actual Results:  
The talkback says it crashed with 2005051906

Expected Results:  
Should have said 2005051005 (this is what profile/compatibility.ini says about
this build)

Comment 1

[Radek 'sysKin' Czyz]

Hm, a typo, should be:

Expected Results:  
Should have said 2005061005 (this is what profile/compatibility.ini says about
this build)

..sorry

Comment 2

[Peter van der Woude [:Peter6]]

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050613
Firefox/1.0+ ID:2005061308

Confirmed for Beast.
I'll need to crash Pacifica first to check what it sends

Comment 3

[Chase Phillips]

pacifica took over beast's duty doing release builds on 5/19.  Since then it
hasn't clobbered its build tree (which leads to Talkback being in the build
along with the old master.ini file).

Comment 4

[Chase Phillips]

I moved beast's build directory aside.  It's not uploading its symbols anyway so
these builds should not have the Talkback client.  After it completes a build on
the next cycle we can verify this.

Comment 5

[Jay Patel [:jay]]

Look in your components directory, check the build id in the master.ini and see
if that matches any crashes you submit with that build.  Thanks.

Comment 6

[Hermann Schwab]

I'm downloading nightlies and sometimes tinderbox builds from Pacifica as zips.
Seems the BuildID of the nightly is used throughout the day:

Nightly:  1.9a1: 2005081307 file date: 13. August 2005 08:07:54
Pacifica: 1.9a1: 2005081307 file date: 13. August 2005 13:16:28
I also saw that latter wrong buildID in a talkback record.

behavior may lead to wrong talkback records, and may be caused by:

Bug 244485 Build ID only generated when MOZILLA_OFFICIAL is set

also related:
Bug 296395  	Improve accuracy of build id

Comment 7

[Hermann Schwab]

(In reply to comment #6)

> Nightly:  1.9a1: 2005081307 file date: 13. August 2005 08:07:54
> Pacifica: 1.9a1: 2005081307 file date: 13. August 2005 13:16:28

Both files were downloaded immediately when being available, and data above is
from Windows Explorer Properties. The pacifica tinderbox was showing check-ins
in the 5 hours between nightly and tinderbox build, so the files differ, the
BuildId not. Using fc /b I found firefox.exe to be different.

Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.9a1) Gecko/20050813 Firefox/1.0+
Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.9a1) Gecko/20050813 Firefox/1.0+

Comment 8

[Hermann Schwab]

seems 
Bug 305233 pacifica tinderbox builds have wrong buildID
is a dupe of this one, but that one is assigned, and has younger comments, otherwise I would have dupe it to this bug.

Comment 9

[J. Paul Reed [:preed]]

I'm resolving this a dup of bug 353747.

Interestingly, we don't use beast anymore, and we only use the VM incarnation of pacifica.

*** This bug has been marked as a duplicate of 353747 ***