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@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

Hi Martin,

I'm not sure what's happening here and I'm not a reprotest expert, but
I couldn't help noticing that it's a different failure on salsa:

https://salsa.debian.org/mdosch/bash-unit/-/jobs/5595184

In particular, whilst there is a traceback on Salsa, it looks like the
package's testsuite is failing and *that* reprotest traceback is a
symptom of that rather than a root cause. Is that observation right?

Either way, if it fails locally on your machine like that, something
is probably wrong...


Best wishes,

 — Chris


ps.

  > […]
  > --vary=-build_path,domain_host.use_sudo=1 --auto-build
  > ~/build/deb/bash-unit_2.3.1-1.dsc
    ^
I wonder if some part of the toolchain doesn't support expanding ~ to
$HOME.

Hi Chris,

Am 05.08.2024 13:17, schrieb Chris Lamb:

yes, the test fails. I already created an issue upstream. But a failing
autopkgtest should not make reprotest traceback I guess.

Good remark, but using the full path doesn't help:

Best regards,
Martin

Martin Dosch wrote:

Thanks for checking. Worth a try — I can never recall the intricacies
of when `os.path.expanduser` is called or implicit. :)


Best wishes,