[08:30] <xypron> I want to run an autopkgtest for the armhf on an arm64 machine. "autopkgtest -U --apt-pocket=proposed -a armhf -s <package>.dsc -- qemu autopkgtest-mantic-armhf.img" times our trying to find the long. It seems to invoke qemu-system-aarch64 with 64 bit EDK II (AAVMF_CODE.fd). man 1 autopkgtest-virt-qemu describes passing additional arguments but current adt_testbed.py only accepts a single argument being the image. Does anybody know the right command for
[08:30] <xypron> running the armhf test?
[08:34] <cpaelzer> xypron: the real tests on armhf do not run in a VM
[08:34] <xypron> cpaelzer: Should I use a schroot?
[08:34] <cpaelzer> they run in armhf containers on arm64 host
[08:35] <cpaelzer> so do you want to "behave like the real armhf test" or "want an armhf emulation VM" ?
[08:36] <xypron> cpaelzer: I want them to stop where they fail for debugging. The closer to real the better.
[08:36] <xypron> cpaelzer: do you know which container to use and how to invoke the autopkgtest inside?
[08:36] <cpaelzer> I made this up here and didn't check my logs, but something like this maybe: autopkgtest -U --apt-pocket=proposed -a armhf -s <package>.dsc --  lxd ubuntu-daily:m
[08:37] <xypron> cpaelzer:  m or mantic?
[08:37] <cpaelzer> ah wait, arch on the container image
[08:38] <cpaelzer> earliest match, either works
[08:38] <cpaelzer> but you need /armhf I guess
[08:38] <cpaelzer> autopkgtest -U --apt-pocket=proposed -a armhf -s <package>.dsc --  lxd ubuntu-daily:mantic/armhf
[08:38] <cpaelzer> If that isn't working I can look how I did it last time (sadly quite a while ago)
[08:41] <cpaelzer> memory is coming back ... you might also need autopkgtest-build-lxd
[08:42] <cpaelzer> IMHO it is always worth to look at the test in question, here a random armhf from autopkgtest ... -- lxd -r lxd-armhf-10.44.124.19 lxd-armhf-10.44.124.19:autopkgtest/ubuntu/mantic/armhf
[08:42] <cpaelzer> obviously we do not have that image remote, hence try with a normal one or fall back creating a special one using the autopkgtest-build-lxd
[08:56] <juliank> normal ones should work ok these days for most cases
[08:57] <cpaelzer> which might be the reason I only faintly remembered autopkgtest-build-lxd for this case
[08:57] <cpaelzer> thanks for confirming juliank
[08:57] <xypron> cpaelzer: "W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/mantic-proposed/InRelease  Could not connect to ports.ubuntu.com:80 (185.125.190.39)" - somehow the network does not work inside LXD
[09:08] <cpaelzer> xypron: I just tested this for you, and since I did I could also write it up for the next one asking
[09:09] <cpaelzer> xypron: this worked for me just now https://github.com/canonical/ubuntu-maintainers-handbook/pull/90
[09:09] -ubottu:#ubuntu-devel- Pull 90 in canonical/ubuntu-maintainers-handbook "Outline manunal armhf autopkgtest" [Open]
[09:10] <cpaelzer> xypron: if networking is still an issue depending on where you run maybe a proxy is needed?
[10:20] <xypron> cpaelzer: 'ufw disable' resolved the issue
[16:27] <rbasak> bryceh: o/ so on a Jammy system, you can run "PYTHONPATH=$PWD/sphinx-design sphinx-build doc/rst _build
[16:27] <rbasak> "
[16:27] <rbasak> And that should build the sphinx docs from the top level of the git-ubuntu tree.
[16:28] <rbasak> This depends on there being a local clone of https://github.com/executablebooks/sphinx-design
[16:28] <rbasak> Or you can do it the virtualenv pip way
[16:28] <rbasak> But I currently do that, with "apt install python-sphinx python-sphinx-rtd-theme" first
[17:47] <sergiodj> @pilot in
[21:26] <sergiodj> @pilot out