Hi Paul, On Sun, Nov 05, 2023 at 01:45:34PM +0100, Paul Gevers wrote: > Source: wasmedge > Version: 0.13.4+dfsg-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: regression > > Dear maintainer(s), > > Your package has an autopkgtest, great. However, it fails. Can you please > investigate the situation and fix it? I copied some of the output at the > bottom of this report. > > The release team has announced [1] that failing autopkgtest on amd64 and > arm64 are considered RC in testing. > > More information about this bug and the reason for filing it can be found on > https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation > > [...] > > 140s # `clang++ --target=wasm32-wasi -o fibonacci.wasm > -mexec-model=reactor script/fibonacci.cpp' failed > 140s # In file included from script/fibonacci.cpp:1: > 140s # script/fibonacci.h:3:10: fatal error: 'cstdint' file not found
Thank you for your report. This is caused #1052002, which I had marked as affects: wasmedge previously. Basically, the autopkgtest compiles a piece of code (with Clang) and tries to run it (with WasmEdge). The Clang++ regression means the code cannot be built. I don't know how you'd like ot handle this w.r.t. the BTS, and testing migrations. I'm inclined to just reassign/merge it to the bug above, but I'll wait for your opinion first. Also, I'm not sure I understand how clang migrated to testing when it introduced an autopkgtest regression in another package. Isn't autopkgtest integration in britney supposed to prevent this kind of thing from happening? Looking for your guidance, Faidon