[Qa-jenkins-scm] Build failed in Jenkins: janitor-worker #929

jenkins at jenkins.debian.net jenkins at jenkins.debian.net
Fri Jun 26 17:40:39 BST 2020


See <https://jenkins.debian.net/job/janitor-worker/929/display/redirect>

Changes:


------------------------------------------
Started by timer
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on osuosl-build167-amd64.debian.net (osuosl167 amd64) in workspace <https://jenkins.debian.net/job/janitor-worker/ws/>
[janitor-worker] $ /bin/sh -xe /tmp/jenkins17475279175931933183.sh
+ /srv/jenkins/bin/jenkins_master_wrapper.sh
Opening branch at https://salsa.debian.org/debian/libsass-python.git/
Cached branch URL https://janitor.debian.net/git/libsass-python,branch=master missing: Branch does not exist: Not a branch: "https://janitor.debian.net/git/libsass-python/": location is a repository.
Total 11378 (delta 6091), reused 11266 (delta 6012), pack-reused 0
Total 32 (delta 7), reused 22 (delta 4), pack-reused 0
Assuming changelog needs to be updated, since it is always changed together with other files in the tree. Specify --no-update-changelog to override.
Building debian packages, running 'sbuild -A -v -c unstable-amd64-sbuild'.
Built libsass-python_0.19.4-0.2~jan+lint1_amd64.changes
Pushing result branch to https://janitor.debian.net/git/libsass-python,branch=lintian-fixes
Elapsed time: 0:15:19.204616
Traceback (most recent call last):
  File "/usr/lib/python3.7/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/usr/lib/python3.7/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/srv/janitor/debian-janitor/janitor/pull_worker.py", line 436, in <module>
    sys.exit(asyncio.run(main()))
  File "/usr/lib/python3.7/asyncio/runners.py", line 43, in run
    return loop.run_until_complete(main)
  File "/usr/lib/python3.7/asyncio/base_events.py", line 584, in run_until_complete
    return future.result()
  File "/srv/janitor/debian-janitor/janitor/pull_worker.py", line 396, in main
    possible_transports=possible_transports))
  File "/usr/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/janitor/debian-janitor/janitor/pull_worker.py", line 180, in run_worker
    possible_transports=possible_transports)
  File "/srv/janitor/debian-janitor/janitor/pull_worker.py", line 142, in push_branch
    overwrite=overwrite, name=branch_name)
  File "/srv/janitor/debian-janitor/breezy/breezy/git/remote.py", line 665, in push_branch
    dw_result = self.send_pack(get_changed_refs, generate_pack_data)
  File "/srv/janitor/debian-janitor/breezy/breezy/git/remote.py", line 479, in send_pack
    generate_pack_data, progress)
  File "/srv/janitor/debian-janitor/dulwich/dulwich/client.py", line 1757, in send_pack
    data=req_data.getvalue())
  File "/srv/janitor/debian-janitor/dulwich/dulwich/client.py", line 1703, in _smart_request
    resp, read = self._http_request(url, headers, data)
  File "/srv/janitor/debian-janitor/breezy/breezy/git/remote.py", line 772, in _http_request
    headers=headers, retries=8)
  File "/srv/janitor/debian-janitor/breezy/breezy/transport/http/__init__.py", line 1851, in request
    response = self._opener.open(request)
  File "/usr/lib/python3.7/urllib/request.py", line 531, in open
    response = meth(req, response)
  File "/srv/janitor/debian-janitor/breezy/breezy/transport/http/__init__.py", line 1719, in http_response
    code, msg, hdrs)
  File "/usr/lib/python3.7/urllib/request.py", line 569, in error
    return self._call_chain(*args)
  File "/usr/lib/python3.7/urllib/request.py", line 503, in _call_chain
    result = func(*args)
  File "/srv/janitor/debian-janitor/breezy/breezy/transport/http/__init__.py", line 1736, in http_error_default
    % (code, msg))
breezy.errors.InvalidHttpResponse: Invalid http response for https://janitor.debian.net/git/libsass-python/git-receive-pack: Unable to handle http code 502: Bad Gateway

SSH EXIT CODE: 1
Build step 'Execute shell' marked build as failure



More information about the Qa-jenkins-scm mailing list