this relates to
https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/2124952 because
it's, in essence, the _same_ issue, but for _tests only_.
tl;dr -- the tests are compiled during the test run. These tests must be
compiled with gcc-14. the real best case is the tests are compiled
exactly the same as what happens during build time. Unfortunately, after
much hacking, i haven't been able to reproduce the exact build, probably
due to the final `find {} exec sed` statement at the end of
dh_auto_override in d/rules. I shoved that in various locations of the
test build, trying to get the path set correctly, and I _still_ end up
with O3 hanging around.
so we end up in a fun world:
1. LTO can get confused easily. we need to use the same toolchains throughout
all builds
2. upstream build files seem to not always respect debian overrides (so setting
an override that'd set O2 doesn't work)
3. maintaining multiple toolchain builds causes maintenance burden
in the end, forcing everything to gcc-14 toolchain seems to solve the
issues. running tests on a subset of architectures, where 03 apparently
does _not_ cause major issues gets tests to pass, but still in a less
than ideal world where tests are compiled 03, binary is compiled 02, and
toolchain differences can easily occur.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2120856
Title:
graphite2: questing autopkgtest failures
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/2120856/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
