Closed
Bug 1262452
Opened 9 years ago
Closed 8 years ago
c-c revision SourceStamp is set to m-c revision in application.ini
Categories
(Thunderbird :: Build Config, defect)
Thunderbird
Build Config
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1267270
People
(Reporter: t.matsuu, Unassigned)
References
Details
(Keywords: regression, regressionwindow-wanted)
Latest comm-central-l10n failed like below:
In the "set props: buildid moz_revision comm_revision" stage, mozilla-central revision is set both comm_revision and moz_revision. This leads a failure in the following "hg update ..." stage.
https://archive.mozilla.org/pub/thunderbird/nightly/2016/04/2016-04-06-03-02-24-comm-central-l10n/comm-central-win32-l10n-nightly-ja-bm94-build1-build25.txt.gz
========= Started set props: buildid moz_revision comm_revision (results: 0, elapsed: 0 secs) (at 2016-04-06 06:03:54.618148) =========
(snip)
moz_revision: '68c0b7d6f16ce5bb023e08050102b5f2fe4aacd8'
comm_revision: '68c0b7d6f16ce5bb023e08050102b5f2fe4aacd8'
========= master_lag: 0.01 =========
========= Finished set props: buildid moz_revision comm_revision (results: 0, elapsed: 0 secs) (at 2016-04-06 06:03:55.075667) =========
========= Started 'hg update ...' failed (results: 2, elapsed: 0 secs) (at 2016-04-06 06:03:55.076645) =========
'hg' 'update' '-C' '-r' '68c0b7d6f16ce5bb023e08050102b5f2fe4aacd8'
in dir c:\builds\moz2_slave\tb-c-cen-w32-l10n-ntly-0000000\build/comm-central (timeout 1200 secs)
Reporter | ||
Comment 1•9 years ago
|
||
(In reply to Takanori MATSUURA from comment #0)
> Latest comm-central-l10n failed like below:
> In the "set props: buildid moz_revision comm_revision" stage,
> mozilla-central revision is set both comm_revision and moz_revision. This
> leads a failure in the following "hg update ..." stage.
>
>
> https://archive.mozilla.org/pub/thunderbird/nightly/2016/04/2016-04-06-03-02-
> 24-comm-central-l10n/comm-central-win32-l10n-nightly-ja-bm94-build1-build25.
> txt.gz
>
> ========= Started set props: buildid moz_revision comm_revision (results: 0,
> elapsed: 0 secs) (at 2016-04-06 06:03:54.618148) =========
> (snip)
> moz_revision: '68c0b7d6f16ce5bb023e08050102b5f2fe4aacd8'
> comm_revision: '68c0b7d6f16ce5bb023e08050102b5f2fe4aacd8'
> ========= master_lag: 0.01 =========
> ========= Finished set props: buildid moz_revision comm_revision (results:
> 0, elapsed: 0 secs) (at 2016-04-06 06:03:55.075667) =========
>
> ========= Started 'hg update ...' failed (results: 2, elapsed: 0 secs) (at
> 2016-04-06 06:03:55.076645) =========
> 'hg' 'update' '-C' '-r' '68c0b7d6f16ce5bb023e08050102b5f2fe4aacd8'
> in dir
> c:\builds\moz2_slave\tb-c-cen-w32-l10n-ntly-0000000\build/comm-central
> (timeout 1200 secs)
Summary: m-c revision is set to c-c revision → m-c revision is set to c-c revision during comm-central-l10n build
Comment 2•8 years ago
|
||
Looks like this is read from application.ini here: https://dxr.mozilla.org/comm-central/source/mail/locales/Makefile.in#145-147
Looking at a current application.ini, the SourceStamp there matches the one in platform.ini, and corresponds to the m-c revision.
So this is actually a c-c build config bug.
Component: General Automation → Build Config
Keywords: regression,
regressionwindow-wanted
Product: Release Engineering → Thunderbird
QA Contact: catlee
Updated•8 years ago
|
Summary: m-c revision is set to c-c revision during comm-central-l10n build → m-c revision is set to c-c revision in application.ini
Updated•8 years ago
|
Summary: m-c revision is set to c-c revision in application.ini → c-c revision SourceStamp is set to m-c revision in application.ini
Comment 3•8 years ago
|
||
Bug 1222878 comment 23:
Latest comm-central-l10n failed like below:
Same revision is set both moz_revision and comm_revision.
https://archive.mozilla.org/pub/thunderbird/nightly/2016/03/2016-03-28-03-02-08-comm-central-l10n/comm-central-win32-l10n-nightly-ja-bm91-build1-build19.txt.gz
(snip)
moz_revision: '63be002b4a803df1122823841ef7633b7561d873'
comm_revision: '63be002b4a803df1122823841ef7633b7561d873'
Takanori, was this actually the first time this failure happened? Then we could deduce a regression window.
Flags: needinfo?(t.matsuu)
Comment 4•8 years ago
|
||
Ah, looks like bug 1267270 is already filed.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(t.matsuu)
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•