New Upstream Snapshot - xrayutilities

• QA Page
• Maintainer email: debian-pan-maintainers@alioth-lists.debian.net
• Automatic publish policy: main: push-derived , pristine-tar: push-derived , upstream: push-derived
• Last processed: 2022-09-03T00:07 (took 6m7s)
• Branch URL: https://salsa.debian.org/science-team/python-xrayutilities.git -b master (taken from version 1.7.4-1)
• Queue position: 251062 (a 277w0d wait)

Schedule a new run

More details

Full run details

Historical runs

• missing-python-distribution: Missing python 3 distribution: h5py
• killed: Command 'SCHROOT=unstable-amd64-sbuild PYTHONPATH=/:/code:/code/breezy:/code/dulwich:/code/lintian-brush:/code/ognibuild:/code/silver-platter:/code/buildlog-consultant:/code/upstream-ontologist:/code/debmutate:/code/python-debian/lib:/usr/lib/python310.zip:/usr/lib/python3.10:/usr/lib/python3.10/lib-dynload:/usr/local/lib/python3.10/dist-packages:/usr/lib/python3/dist-packages /usr/bin/python3 -m janitor.dist --packaging=/tmp/janitorx85obdyb/xrayutilities/debian' returned non-zero exit status 137.
• build-failed-stage-post-build: E ImportError: cannot import name 'cxrayutilities' from partially initialized module 'xrayutilities' (most likely due to a circular import) (/usr/lib/python3/dist-packages/xrayutilities/__init__.py)
• killed: Command 'SCHROOT=unstable-amd64-sbuild PYTHONPATH=/:/code:/code/breezy:/code/dulwich:/code/lintian-brush:/code/ognibuild:/code/silver-platter:/code/buildlog-consultant:/code/upstream-ontologist:/code/debmutate:/code/python-debian/lib:/usr/lib/python310.zip:/usr/lib/python3.10:/usr/lib/python3.10/lib-dynload:/usr/local/lib/python3.10/dist-packages:/usr/lib/python3/dist-packages /usr/bin/python3 -m janitor.dist --packaging=/tmp/janitoraciu2gr_/xrayutilities/debian' returned non-zero exit status 137.
• build-failed-stage-build: E AssertionError: 0.04237466264781992 != 0.04237550721678818 within 9 places (8.445689682543001e-07 difference)
• worker-exception: EOF occurred in violation of protocol (_ssl.c:2396)
• run-disappeared: Worker started processing new run rather than b0073019-f06e-4208-a39c-1c4221f9aeea