Hi Petter,
On 2026-05-06 23:45, Trupti wrote:
Hi Petter,
On 2026-05-06 11:56, Petter Reinholdtsen wrote:
[Trupti]
I will investigate this issue and share any findings soon.
Thank you very much.
You're welcome.
It is worth noting that when I do a test build on the porterbox
platti.debian.org, the entire build including running the tests take
53
minutes, as I could just confirm in a test build this morning.
I simply do not understand why the tests take so long when running
from
autopkgtest, as it is the same set of tests.
I am looking into the FPGA tool chain these days, and ppc64el prove to
be really problematic. :)
Thanks for the inputs.
I manually tried running testsuite of yosyos package on my local
ppc64el machines and didn't get any timeout issue.
Below was the time taken by p9 and p10 system.
POWER10 system:
- debian/tests/yosys-testsuite: 32 minutes 34 seconds
POWER9 system
- debian/tests/yosys-testsuite: 64 minutes 18 seconds
On both systems tests passed successfully, which aligns with your
53-minute result on platti.debian.org
So I guess this does not appear to be a misaligned memory access issue
on ppc64el.
I am looking into how we can avoid timeout issue.
Thanks,
Trupti
I noticed the tests are currently running one-by-one, which makes the
execution quite slow.
I tried running them in parallel by changing:
make vanilla-test => make -j6 vanilla-test
On my system, this reduced the runtime from around 64 minutes to about
11 minutes.
Do you think using parallelism here would be acceptable? If yes, this
might help avoid the CI timeout issue.
Thanks,
Trupti
