1385053 - Windows buildbot builds fail on try due to missing ccache

Status: RESOLVED WONTFIX

(Release Engineering :: General, defect)

Description

[(no longer active)]

See this try push from a m-c revision: https://treeherder.mozilla.org/#/jobs?repo=try&revision=77724711a6cc9cf63d14f09da596e0d525688ca2

Log: https://archive.mozilla.org/pub/firefox/try-builds/[e-mail]-77724711a6cc9cf63d14f09da596e0d525688ca2/try-win64/try-win64-bm78-try1-build10554.txt.gz

11:25:31     INFO -  DEBUG: ccache: Trying c:/builds/moz2_slave/try-w64-0000000000000000000000/build/src/sccache2/sccache
11:25:31     INFO -  ERROR: Cannot find ccache
11:25:31     INFO -  *** Fix above errors and then restart with\
11:25:31     INFO -                 "c:/builds/moz2_slave/try-w64-0000000000000000000000/build/src/mozmake.EXE -f client.mk build"
11:25:31     INFO -  client.mk:379: recipe for target 'configure' failed
11:25:31     INFO -  mozmake.EXE: *** [configure] Error 1

Comment 1

[Justin Wood (:Callek)]

(In reply to :Ehsan Akhgari (needinfo please, extremely long backlog) from comment #0)
> See this try push from a m-c revision:
> https://treeherder.mozilla.org/#/
> jobs?repo=try&revision=77724711a6cc9cf63d14f09da596e0d525688ca2
> 

This is failing because of a change that glandium made on central now that we're not using BB for production builds on mozilla-central.

That said, we're leaving BB builds enabled on try to facilitate pushes from old revs (before the taskcluster switch) and for pushes from older trees.

I can easily see how this could be confusing to people though, and as such, :glandium is there anything we can reasonably do to lessen the impact of this in current trees until we shut down try's buildbot?

(One thought I have is to embed a new mozconfig like "bb-mozconfig" that includes (older) ccache?)  Another thought may be hiding the BB builds on try, but then that partly defeats the purpose of letting people push and see it there.

Comment 2

[Mike Hommey [:glandium]]

The problem is that it's sccache today, but it's going to be rust tomorrow, and continuing to update tooltool every time we change toolchains until buildbot dies for good is not really enticing.

Comment 4

[Michael Froman [:mjf]]

Unfortunately, seeing a busted build causes me (possibly other dev) to spend extra time figuring out what I messed up.  It would be nice if the failure could be reported differently in some way to indicate a known issue or a temporary issue.

Comment 5

[Nico Grunbaum [:ng, @chew:mozilla.org]]

A warning banner at the top of Try results would go a long way.

Comment 6

[Kim Moir [:kmoir] ET]

There is also bug 1384706, trychooser should not enable windows bb builds by default.

Comment 7

[(no longer active)]

(In reply to Kim Moir [:kmoir] ET from comment #6)
> There is also bug 1384706, trychooser should not enable windows bb builds by
> default.

Note that I use the "T" push which is supposed to be the responsible way to do try pushes, so it's not just -b all.

Comment 8

[Chris AtLee [:catlee]]

buildbot is gone