autopkgtests fail on s390x (segfault)
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Ubuntu on IBM z Systems |
Triaged
|
Undecided
|
bugproxy | |||
libtraceevent (Ubuntu) | Status tracked in Plucky | |||||
Noble |
New
|
Undecided
|
Unassigned | |||
Oracular |
New
|
Undecided
|
Unassigned | |||
Plucky |
Fix Released
|
Undecided
|
Unassigned | |||
libtracefs (Ubuntu) | Status tracked in Plucky | |||||
Noble |
New
|
Undecided
|
Unassigned | |||
Oracular |
New
|
Undecided
|
Unassigned | |||
Plucky |
Fix Released
|
Undecided
|
Adrien Nader |
Bug Description
As part of the added QA to libtracefs it was found that it triggers a segfault on s390x.
This isn't just a test failing, it seems this is still deeply broken on s390x.
Either way, while in the time pressure of the noble release the decision was simplified like "The tests didn't make it worse, just now we know" and continued (To not leave these platforms behind later unable to add it, albeit knowing it is still incomplete for now).
It does not mean that we can ignore them for too long and certainly need to work on completing that into being fully functional in tests and real usage. Hence we create this spin off bug from the MIR work in bug 2051925 for tracking the further efforts.
Example test log:
https:/
Related branches
- Ubuntu Sponsors: Pending requested
- git-ubuntu import: Pending requested
-
Diff: 73 lines (+42/-1)4 files modifieddebian/changelog (+8/-0)
debian/control (+2/-1)
debian/patches/0002-fix-file-endianness.patch (+31/-0)
debian/patches/series (+1/-0)
Changed in ubuntu-z-systems: | |
assignee: | nobody → bugproxy (bugproxy) |
tags: | added: reverse-proxy-bugzilla |
tags: | added: rls-oo-incoming |
tags: | added: architecture-s39064 bugnameltc-206054 severity-high targetmilestone-inin--- |
tags: |
added: foundations-todo removed: rls-oo-incoming |
Changed in ubuntu-z-systems: | |
status: | New → Triaged |
Changed in libtracefs (Ubuntu): | |
status: | New → Triaged |
I'll assign Adrien as the agreement on the MIR was to follow up on these, but also Frank to sync this with IBM for their input which TBH could be anything from "here is the fix" to a worse "it will never work please remove it"
Also there is a sibling of this for ppc64el in bug 2062119