Bug#1055392: wasmedge: autopkgtest regression: 'cstdint' file not found
Control: affects 1052002 - wasmedge Control: affects 1052002 + src:wasmedge On Thu, Nov 09, 2023 at 09:52:04AM +0100, Paul Gevers wrote: > > Hi Paul, > > Thank you for your report. This is caused #1052002, which I had marked > > as affects: wasmedge previously. > > Sorry for not checking that, but because you marked it as affecting the > *binary* package wasmedge, it doesn't show up looking for bugs in the source > package wasmedge (that may be a bts bug). Because this is a FTBFS issue, I > recommend you to mark it affects src:wasmedge instead of wasmedge. Alright, fair enough. Hopefully fixed above? > > 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? > > britney prevents this kind of things currently only for *direct* reverse > (test) dependencies. In this case we have: > > test/Depends: clang (from src:llvm-defaults) -> (Depends) clang-16 > > As I'm pretty sure you meant not clang, but one of the versioned clang > packages, britney didn't see the breakage. There are multiple ways to > improve this: > * britney should look at all transitive dependencies (we lack the resources > and also not environmentally friendly) > * britney could be taught to translate (automatically or via configuration) > "-defaults" packages to their real packages. This would be good for multiple > ecosystems, patches welcome. > * Individual packages that are sensitive could use the > `hint-testsuite-triggers` trick from the autopkgtest spec [1] and add the > current real packages. That's a PITA to maintain though, and adding versions > that you don't really test is wrong. Hrm, that's useful context and in hindsight makes a lot of sense. Thanks so much for spending the time to explain this to me! In the meantime, I'll mark the embed-cxx test as flaky in the next WasmEdge upload until the clang-16 bug gets fixed. Best, Faidon
Bug#1055392: wasmedge: autopkgtest regression: 'cstdint' file not found
Hi Faidon, On 05-11-2023 21:41, Faidon Liambotis wrote: Hi Paul, Thank you for your report. This is caused #1052002, which I had marked as affects: wasmedge previously. Sorry for not checking that, but because you marked it as affecting the *binary* package wasmedge, it doesn't show up looking for bugs in the source package wasmedge (that may be a bts bug). Because this is a FTBFS issue, I recommend you to mark it affects src:wasmedge instead of wasmedge. 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. That's probably OK, I see you already did that. 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? britney prevents this kind of things currently only for *direct* reverse (test) dependencies. In this case we have: test/Depends: clang (from src:llvm-defaults) -> (Depends) clang-16 As I'm pretty sure you meant not clang, but one of the versioned clang packages, britney didn't see the breakage. There are multiple ways to improve this: * britney should look at all transitive dependencies (we lack the resources and also not environmentally friendly) * britney could be taught to translate (automatically or via configuration) "-defaults" packages to their real packages. This would be good for multiple ecosystems, patches welcome. * Individual packages that are sensitive could use the `hint-testsuite-triggers` trick from the autopkgtest spec [1] and add the current real packages. That's a PITA to maintain though, and adding versions that you don't really test is wrong. Paul [1] https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/doc/README.package-tests.rst OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1055392: wasmedge: autopkgtest regression: 'cstdint' file not found
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
Bug#1055392: wasmedge: autopkgtest regression: 'cstdint' file not found
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 Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/w/wasmedge/39560218/log.gz 140s autopkgtest [15:12:57]: test embed-cxx: [--- 140s 1..4 140s not ok 1 build fibonacci.cpp to wasm 140s # (in test file debian/tests/embed-cxx, line 12) 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 140s # #include 140s # ^ 140s # 1 error generated. 140s ok 2 build fibonacci/cpp to native 141s ok 3 build embed_cxx 141s not ok 4 run embed_cxx and test for valid output 141s # (in test file debian/tests/embed-cxx, line 27) 141s # `assert_line --index 2 --partial "3524578"' failed 141s # 141s # -- line does not contain substring -- 141s # index : 2 141s # substring : 3524578 141s # line : [2023-11-04 15:12:58.648] [error] loading failed: invalid path, Code: 0x20 141s # -- 141s # 141s autopkgtest [15:12:58]: test embed-cxx: ---] OpenPGP_signature.asc Description: OpenPGP digital signature