1185429 - Try build keeps failing with empty failure summary (log contains "can't open file 'scripts/scripts/fx_desktop_build.py'")

Status: RESOLVED INVALID

(Release Engineering :: Applications: MozharnessCore, defect)

Description

[Botond Ballo [:botond]]

I have a patch that I've tried to push to Try several times over the weekend, but the build keeps failing with an empty summary. The log contains the error:

/tools/buildbot/bin/python: can't open file 'scripts/scripts/fx_desktop_build.py': [Errno 2] No such file or directory

Here are my failing pushes:
  https://treeherder.mozilla.org/#/jobs?repo=try&revision=32d0ba6b5c57
  https://treeherder.mozilla.org/#/jobs?repo=try&revision=411545300621
  https://treeherder.mozilla.org/#/jobs?repo=try&revision=44bffc2e0b9a

Interestingly, a different patch I pushed to Try over the weekend built fine:
  https://treeherder.mozilla.org/#/jobs?repo=try&revision=9d125020356c

Looking at https://treeherder.mozilla.org/#/jobs?repo=try, other people's Try pushes seem to be working fine as well - I'm not sure what it is about my pushes that's triggering this problem.

Comment 1

[Rail Aliiev [:rail]]

Sounds like related to in-tree mozharnes. Jordan, can you take a look?

Comment 2

[Nicolas Vigier]

I have a similar problem. Some examples:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=38759b7ff9f5
https://treeherder.mozilla.org/#/jobs?repo=try&revision=ad419710b483
https://treeherder.mozilla.org/#/jobs?repo=try&revision=23c37d395786

I don't know if that's related to what is triggering the problem, but the trees I'm pushing are based on the esr38 branch.

Comment 3

[Jordan Lund (:jlund)]

> I don't know if that's related to what is triggering the problem, but the
> trees I'm pushing are based on the esr38 branch.

yes this is due to in-tree mozharness: 

your esr38 copy isn't up to date with http://hg.mozilla.org/releases/mozilla-esr38/ as you can see it's missing the mozharness copy: https://hg.mozilla.org/try/file/38759b7ff9f5/testing/mozharness

is it possible to update to a point where we added mozharness in-tree (July 8th/9th)?
    - mozharness landed on esr38: http://hg.mozilla.org/releases/mozilla-esr38/rev/71cb931993e7
    - latest update to mozharness on esr38: http://hg.mozilla.org/releases/mozilla-esr38/rev/b7d944b2b418

updating to b7d944b2b418 is preferable if possible. If you can not, I can help point you to the patches you need to cherry pick.

Comment 4

[Botond Ballo [:botond]]

You're right, the difference between the problematic patch and the others is that the problematic patch is based on a tree that's older than July 8. I will pull/rebase and see if that fixes the problem.

Comment 5

[Botond Ballo [:botond]]

(In reply to Botond Ballo [:botond] from comment #4)
> You're right, the difference between the problematic patch and the others is
> that the problematic patch is based on a tree that's older than July 8. I
> will pull/rebase and see if that fixes the problem.

That did indeed fix the problem (new Try push https://treeherder.mozilla.org/#/jobs?repo=try&revision=cce7dd5802c8 looks much better), thanks!

I'm going to close this bug as invalid, as apparently pushing to Try from a tree that's too old is not supported, and that's what I was doing. If you feel a different resolution is more appropriate, please change accordingly.

Comment 6

[Nicolas Vigier]

(In reply to Jordan Lund (:jlund) from comment #3)
> 
> updating to b7d944b2b418 is preferable if possible. If you can not, I can
> help point you to the patches you need to cherry pick.

Thanks. I will cherry pick the commits adding/updating the in-tree mozharness for now (until we switch to 38.2.0esr).