1962499 - Windows CI Machines are broken

Status: RESOLVED FIXED

(NSS :: Test, defect, P1)

Description

[Dennis Jackson]

All the Windows builds are broken. Example Job

I took a brief look and saw that in automation/taskcluster/windows/setup.sh, the paths to Python are wrong and need to be updated:

-/c/mozilla-build/python/python.exe /c/builds/tooltool.py -c /c/builds/tooltool_cache --url ${TASKCLUSTER_PROXY_URL}/tooltool.mozilla-releng.net/ --overwrite -m $(dirname $0)/releng.manifest fetch
+/c/mozilla-build/python3/python3.exe /c/builds/tooltool.py -c /c/builds/tooltool_cache --url ${TASKCLUSTER_PROXY_URL}/tooltool.mozilla-releng.net/ --overwrite -m $(dirname $0)/releng.manifest fetch

However, this still errors out with tooltool.py missing as in this log. I don't see any obvious changes in NSS or in mozilla-central that would cause this, but I'm guessing some tooling somewhere changed.

@Julien - It looks like you've worked on tooltool before, would you be able to take a look?

Comment 1

[Dennis Jackson]

Attachment: Bug 1962499 - Fix Windows CI builds. r=#nss-reviewers

Comment 2

[Julien Cristau [:jcristau]]

The windows worker image was updated in https://github.com/mozilla-releng/fxci-config/pull/327 on March 27, which looks like it matches when nss builds broke.
@jmoss, did tooltool.py get removed (or moved?) intentionally in that update?

Comment 3

[:jmoss]

tooltool.py is located at C:\mozilla-build\tooltool.py although setup.sh is pointed to /c/builds/tooltool.py.

Comment 4

[Dennis Jackson]

Thanks Julien, jmoss. That's fixed the builds.

Is there something we can do to avoid this happening in the future? Would it be feasible to register the NSS tests with whatever process releng use to validate changes to worker configurations for mozilla-unified?

Comment 5

[Julien Cristau [:jcristau]]

Filed as bug 1963058.

Comment 6

[Dennis Jackson]

https://hg-edge.mozilla.org/projects/nss/rev/6c3f39b32e5b5e394dea989becd21fde6d8cede9