1485187 - Document what to do for known classes of Tup build bustage

Status: RESOLVED FIXED

(Firefox Build System :: General, enhancement)

Description

[Chris Manchester (limited bugmail, email directly)]

There are two cases of tup build bustage we've seen that we're likely to encounter again that should be documented, probably prior to bumping Btup to tier 1.

The first is when cargo build script start generating new outputs. The newly generated file names need to be added to python/mozbuild/mozbuild/backend/cargo_build_defs.py so tup knows about them.

The second is when some aspect of the build system that has handling in both make and tup backends sees some re-structuring, in particular this has come up when changing the invocations for xpidl/ipdl/webidl handling.

Comment 1

[Chris Manchester (limited bugmail, email directly)]

Attachment: Bug 1485187 - Document known failure scenarios for Tup automation builds.

Comment 2

[Michael Shal [:mshal]]

Comment on attachment 9008543 [details]
Bug 1485187 - Document known failure scenarios for Tup automation builds.

Michael Shal [:mshal] has approved the revision.

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/8f15b7b4362d
Document known failure scenarios for Tup automation builds. r=mshal

Comment 4

[Arthur Iakab [arthur_iakab]]

https://hg.mozilla.org/mozilla-central/rev/8f15b7b4362d