1883146 - mach bootstrap fails at artifact_commands.py

Status: RESOLVED INVALID

(Firefox Build System :: Bootstrap Configuration, defect, P5)

Description

[Amanita]

Steps to reproduce:

downloaded bootstrap.py, ran it, in mozilla-unified ran ./mach bootstrap and chose mode 2 (desktop, no artifacts)

Actual results:

It failed at this:

Setting up artifact nasm.tar.zst
Downloading artifact to local cache: /var/home/user/Distrobox/Fedora/.mozbuild/toolchains/d2f2f30c2456a8f1-nasm.tar.zst
Downloading... 0.0 %
Downloading... 100.0 %
rm tree: /var/home/user/Distrobox/Fedora/.mozbuild/nasm
untarring "/var/home/user/Distrobox/Fedora/.mozbuild/nasm.tar.zst"
Error running mach:

    mach --log-no-times artifact toolchain --from-task caebBgssRaSbCr5NfZY4RQ:public/build/sysroot-wasm32-wasi.tar.zst

The error occurred in code that was called by the mach command. This is either
a bug in the called code itself or in the way that mach is calling it.
You can invoke ``./mach busted`` to check if this issue is already on file. If it
isn't, please use ``./mach busted file artifact`` to report it. If ``./mach busted`` is
misbehaving, you can also inspect the dependencies of bug 1543241.

If filing a bug, please include the full output of mach, including this error
message.

The details of the failure are as follows:

requests.exceptions.ConnectTimeout: HTTPSConnectionPool(host='firefox-ci-tc.services.mozilla.com', port=443): Max retries exceeded with url: /api/queue/v1/task/caebBgssRaSbCr5NfZY4RQ/artifacts/public/chain-of-trust.json (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7f02aed8f260>, 'Connection to firefox-ci-tc.services.mozilla.com timed out. (connect timeout=None)'))

  File "/var/home/user/Firefox-Build/mozilla-unified/python/mozbuild/mozbuild/artifact_commands.py", line 496, in artifact_toolchain
    record = ArtifactRecord(task_id, name)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/var/home/user/Firefox-Build/mozilla-unified/python/mozbuild/mozbuild/artifact_commands.py", line 334, in __init__
    cot = cache._download_manager.session.get(
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/var/home/user/Firefox-Build/mozilla-unified/third_party/python/requests/requests/sessions.py", line 602, in get
    return self.request("GET", url, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/var/home/user/Firefox-Build/mozilla-unified/third_party/python/requests/requests/sessions.py", line 589, in request
    resp = self.send(prep, **send_kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/var/home/user/Firefox-Build/mozilla-unified/third_party/python/requests/requests/sessions.py", line 703, in send
    r = adapter.send(request, **kwargs)
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/var/home/user/Firefox-Build/mozilla-unified/third_party/python/requests/requests/adapters.py", line 507, in send
    raise ConnectTimeout(e, request=request)

Comment 1

[BugBot [:suhaib / :marco]]

The Bugbug bot thinks this bug should belong to the 'Firefox Build System::Bootstrap Configuration' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Alex Hochheiden [:ahochheiden] [he/him]]

Can you consistently reproduce this? Based on the error message, I'd reckon this is probably a one-off issue/was due an intermittent internet connectivity issue at the time.

Comment 3

[Amanita]

no I was able to reproduce this another time.

I probably tried to boostrap using mercurial, deleted the dir, bootstrap with git, deleted, bootstrap with mercurial again or something like that.

I did not interact with mercurial or git, just remove the directory. But everything downloads normally, and I also redownloaded bootstrap.py to be the vanilla one.

This is in a Fedora 39 toolbox, before I tried to edit the bootstrap.py to bootstrap the bookmarks/release directly, did not work and got a tip to use checkout to do that. So I removed that, redownloaded bootstrap.py and ran it again, everything default.

Everything went well until close before the end where this happened.

Comment 4

[Alex Hochheiden [:ahochheiden] [he/him]]

I don't think there's anything for us to do here.

If you can consistently reproduce this, please re-open this bug, otherwise, I think it was just a connection issue on your end that did not occur the next time you ran bootstrap.