[08:30] I want to run an autopkgtest for the armhf on an arm64 machine. "autopkgtest -U --apt-pocket=proposed -a armhf -s .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] running the armhf test? [08:34] xypron: the real tests on armhf do not run in a VM [08:34] cpaelzer: Should I use a schroot? [08:34] they run in armhf containers on arm64 host [08:35] so do you want to "behave like the real armhf test" or "want an armhf emulation VM" ? [08:36] cpaelzer: I want them to stop where they fail for debugging. The closer to real the better. [08:36] cpaelzer: do you know which container to use and how to invoke the autopkgtest inside? [08:36] I made this up here and didn't check my logs, but something like this maybe: autopkgtest -U --apt-pocket=proposed -a armhf -s .dsc -- lxd ubuntu-daily:m [08:37] cpaelzer: m or mantic? [08:37] ah wait, arch on the container image [08:38] earliest match, either works [08:38] but you need /armhf I guess [08:38] autopkgtest -U --apt-pocket=proposed -a armhf -s .dsc -- lxd ubuntu-daily:mantic/armhf [08:38] If that isn't working I can look how I did it last time (sadly quite a while ago) [08:41] memory is coming back ... you might also need autopkgtest-build-lxd [08:42] 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] 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] normal ones should work ok these days for most cases [08:57] which might be the reason I only faintly remembered autopkgtest-build-lxd for this case [08:57] thanks for confirming juliank [08:57] 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] xypron: I just tested this for you, and since I did I could also write it up for the next one asking [09:09] 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] xypron: if networking is still an issue depending on where you run maybe a proxy is needed? [10:20] cpaelzer: 'ufw disable' resolved the issue [16:27] bryceh: o/ so on a Jammy system, you can run "PYTHONPATH=$PWD/sphinx-design sphinx-build doc/rst _build [16:27] " [16:27] And that should build the sphinx docs from the top level of the git-ubuntu tree. [16:28] This depends on there being a local clone of https://github.com/executablebooks/sphinx-design [16:28] Or you can do it the virtualenv pip way [16:28] But I currently do that, with "apt install python-sphinx python-sphinx-rtd-theme" first [17:47] @pilot in === ChanServ changed the topic of #ubuntu-devel to: Archive: Mantic Open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Bionic-Lunar | Patch Pilots: sergiodj === Adri2000_ is now known as Adri2000 [21:26] @pilot out === ChanServ changed the topic of #ubuntu-devel to: Archive: Mantic Open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Bionic-Lunar | Patch Pilots: N/A