Differentiating I/II/III
The syscall assertion does only happen in manual runs. My environment and start
commands might not yet be perfect. But what surely hits exactly when the real
test fails is the User process fault.
On x86 where the test works fine this syscall messages also appear, so
"Theory II (syscall)" might be a red herring and will be ignored for now.
If it is related to LTO can be tested via d/rules by adding
export DEB_BUILD_MAINT_OPTIONS=hardening=+all optimize=-lto
I've built chrony one with that applied and retried the test.
In that case the test works just fine \o/.
So indeed there is an issue with LTO, the user space crash no more occurs.
We will need:
- an upload to chrony to avoid it will be LTO buillt to avoid this
- an upstream report about the problem so that they can look into what
might fail
** Changed in: chrony (Ubuntu)
Status: New => Triaged
** Changed in: chrony (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921377
Title:
upstream-simulation-test-suite test fails on s390x with LTO turned on
in dpkg
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1921377/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
