Bug#1077873: reprotest: Traces back when trying to do a test

Martin Dosch martin at mdosch.de
Sat Aug 3 21:31:21 BST 2024


Package: reprotest
Version: 0.7.27
Severity: important

Dear Maintainer,

due to the excellent feedback from Phil Wyett in #1061087 I wanted to 
reproduce the issue with reprotest but it bails out with a traceback:

```
martin at schlepptop /tmp/bash-unit-testing % sudo reprotest --vary=-build_path,domain_host.use_sudo=1 --auto-build ~/build/deb/bash-unit_2.3.1-1.dsc
WARNING:reprotest:The control build runs on 1 CPU by default, give --min-cpus to increase this.
dpkg-source: error: cannot fstat file ./bash-unit_2.3.1.orig.tar.gz: No such file or directory
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 862, in run
    return 0 if check_func(*check_args) else 1
                ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 410, in check_auto
    dist_x0 = proc.send(("control", var_x0))
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 339, in corun_builds
    bctx.run_build(testbed, build, os.environ, artifact_pattern, testbed_build_pre, no_clean_on_error)
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 218, in run_build
    testbed.check_exec2(build_argv,
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 59, in check_exec2
    (code, out, err) = self.execute(argv,
                       ^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/reprotest/lib/adt_testbed.py", line 494, in execute
    self.bomb('testbed auxverb failed with exit code %i' % proc.returncode)
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 70, in bomb
    raise _type(m)
reprotest.lib.adtlog.TestbedFailure: testbed auxverb failed with exit code 255
```

I copied the file bash-unit_2.3.1.orig.tar.gz into the folder as it said 
it was missing it, but it didn`t change anything and it traced back 
again with the same traceback as shown above.

Best regards,
Martin

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (900, 'testing'), (600, 'unstable'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'experimental'), (1, 'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.9.10-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages reprotest depends on:
ii  apt-utils              2.9.7
ii  libdpkg-perl           1.22.11
ii  procps                 2:4.0.4-5
ii  python3                3.12.4-1
ii  python3-debian         0.1.49
ii  python3-distro         1.9.0-1
ii  python3-pkg-resources  70.3.0-2
ii  python3-rstr           3.2.2-1

Versions of packages reprotest recommends:
ii  diffoscope-minimal  273
ii  disorderfs          0.5.11-3+b1
ii  faketime            0.9.10-2.2
ii  locales-all         2.39-6
ii  sudo                1.9.15p5-3+b1

Versions of packages reprotest suggests:
ii  autodep8     0.28+nmu1
pn  qemu-system  <none>
ii  qemu-utils   1:9.0.2+ds-1
ii  schroot      1.6.13-3+b3

-- no debconf information


More information about the Reproducible-builds mailing list