Closed Bug 1283438 Opened 8 years ago Closed 8 years ago

Android Nightly Trunk Builds fail with No rule to make target `/builds/slave/m-cen-and-api-15-l10n_2-000000/build/mozilla-central/obj-l10n/dist/fennec-50.0a1.en-US.android-arm.apk', needed by `/builds/slave/m-cen-and-api-15-l10n_2-000000/build/mozilla-cen

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(firefox50 fixed)

RESOLVED FIXED
Tracking Status
firefox50 --- fixed

People

(Reporter: cbook, Assigned: Callek)

References

()

Details

Attachments

(1 file)

04:48:17 ERROR - make: *** No rule to make target `/builds/slave/m-cen-and-api-15-l10n_2-000000/build/mozilla-central/obj-l10n/dist/fennec-50.0a1.en-US.android-arm.apk', needed by `/builds/slave/m-cen-and-api-15-l10n_2-000000/build/mozilla-central/obj-l10n/dist/l10n-stage/fennec'. Stop.

https://treeherder.mozilla.org/logviewer.html#?job_id=4194500&repo=mozilla-central#L4412

seems several android nightlys failed on m-c today.
Needed because buildbot clones/checks out from the repo head (of default)
and then updates to the rev for the nightly we're pulling, which can cause
CLOBBER file changes to initiate an unwanted clobber of the object directory
where we just pulled the nightly binary from. Even when CLOBBER hasn't actually
been touched in the changeset range we're looking at between nightlies.

Review commit: https://reviewboard.mozilla.org/r/61610/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/61610/
Attachment #8766892 - Flags: review?(mh+mozilla)
After chatting on IRC today, we found the problem, which was the CLOBBER file in a changeset closer to HEAD than the nightlies themselves had changed.

Because we configure then do the wget, then pull then update then configure again it caused us to clobber the object directory over again and thus fail.

This is a stop-gap to making us just use the rev the nightly is on to begin with.... So we can not fail (as much) :-)
I think it's worth adding that buildbot does check out mozilla-central from the version of nightly. mozharness then checks out mozilla-central from the default branch.
(In reply to Axel Hecht [:Pike] from comment #3)
> I think it's worth adding that buildbot does check out mozilla-central from
> the version of nightly. mozharness then checks out mozilla-central from the
> default branch.

Not quite, buildbot uses archiver to grab the mozharness scripts from the version of the nightly... and mozharness does the checkout to default.
Comment on attachment 8766892 [details]
Bug 1283438 - Set AUTOCLOBBER to empty for l10n .

https://reviewboard.mozilla.org/r/61610/#review58500

::: browser/config/mozconfigs/linux32/l10n-mozconfig:18
(Diff revision 1)
>  
>  ac_add_options --disable-stdcxx-compat
>  
> +# Don't autoclobber l10n, as this can lead to missing binaries and broken builds
> +# Bug 1283438
> +mk_add_options AUTOCLOBBER=

One concern is if this means those builds are never going to be clobbered. OTOH, the CLOBBER file is not involved in the things that could cause problems by not clobbering those builds...
Attachment #8766892 - Flags: review?(mh+mozilla) → review+
Pushed by Callek@gmail.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/e0e56c2e1881
Set AUTOCLOBBER to empty for l10n r=glandium.
(In reply to Mike Hommey [:glandium] from comment #5)
> Comment on attachment 8766892 [details]
> Bug 1283438 - Set AUTOCLOBBER to empty for l10n .
> 
> 
> One concern is if this means those builds are never going to be clobbered.
> OTOH, the CLOBBER file is not involved in the things that could cause
> problems by not clobbering those builds...

We do have clobberer that can still clobber them if we need to.
https://hg.mozilla.org/mozilla-central/rev/e0e56c2e1881
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Assignee: nobody → bugspam.Callek
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: