Closed Bug 81344 Opened 23 years ago Closed 18 years ago

win32 Build ID discrepancies

Categories

(SeaMonkey :: Build Config, defect, P3)

x86
Windows 98
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME
mozilla1.7alpha

People

(Reporter: doctor__j, Unassigned)

References

Details

(Keywords: polish)

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9+) Gecko/20010516
BuildID:    2001051604

This is annoying and I rely on this when submitting bug reports, pin-pointing
exactly which build I am using.

This is counter-productive if the build you are referring to is NOT the build I
am talking about.  We are looking at the same build ID on the titlebar but it
_isn't_ actually.  It's just like you are talking in inches while I am talking
in centimetres.

Take this two builds as example.  They all give me the same Build ID:
2001051604.  What I concern is the last two digits - "04".

http://ftp.mozilla.org/pub/mozilla/nightly/2001-05-16-17-trunk/mozilla-win32.zip
http://ftp.mozilla.org/pub/mozilla/nightly/2001-05-16-05-trunk/mozilla-win32.zip

Forgive my lack of understanding on how those Build IDs got "etched" on the
titlebar when they are being compiled.  Can anybody tell me how the last two
digits are interpreted???
not sure if this is a valid bug or not.  reassigning to leaf.
Assignee: cls → leaf
Priority: -- → P3
Summary: Nightly Build ID discrepancies → win32 Build ID discrepancies
Target Milestone: --- → mozilla1.0
accepting, i'm going to try and verify this.
Status: NEW → ASSIGNED
*** Bug 83374 has been marked as a duplicate of this bug. ***
It's getting worse. Today (06/20) Win32 installer build has User-String:
Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:0.9.1+) Gecko/20010618
and Build ID: 2001061804

Seems we are two days late :-(
Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 
(you can query for this string to delete spam or retrieve the list of bugs I've 
moved)
Target Milestone: mozilla1.0 → mozilla1.0.1
Out of curiosity, which of these is the "correct" Build ID -- the titlebar Build
ID or the (\bin\components\master.ini) Build ID?
this is a real problem - the cause is the buildID is only opdated on a a clobber
build

the following files all set buildID as uses is various parts of mozilla:

config/build_number
config/nsBuildID.h
content/build/gbdate.h

BUILD_OFFICIAL creates them if missing but doesn't update if they exist
Additionally, w/ Talkback enabled, on a crash, Talkback reports a different
Build ID than the titlebar. For example, right now my titlebar says 2002052306,
but when it crashes, Talkback reports it as 2002052308. Which is it? :) 

See Talkback ID TB6883731Z
Target Milestone: mozilla1.0.1 → mozilla1.7alpha
Assignee: leaf → cmp
Status: ASSIGNED → NEW
Product: Browser → Seamonkey
As the titlebar no longer displays the build ID, I have no way of confirming
whether this bug still exists. Can anyone shed light on this issue? Are builds
produced the same way or can this bug be closed?

Essentially, in comment #8, I was curious as to whether Talkback was indeed
grabbing the correct build ID.
Mass reassign of open bugs for chase@mozilla.org to build@mozilla-org.bugs.
Assignee: chase → build
WFM; reopen if you have a recent build showing build ID inconsistencies.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.