debcrafters-packages team mailing list archive

[John Chittum <2062119@xxxxxxxxxxxxxxxxxx>]

This still occurs on Questing, 25.10. The same issues are being seen on
s390x. This does not appear to happen on amd64 tests. Example of a
recent s390x test failure.

https://autopkgtest.ubuntu.com/results/autopkgtest-
questing/questing/s390x/libt/libtracefs/20250806_105223_0f707@/log.gz

Consistent failing in test_instance_follow_events_clear() in this block:
	
/* Stir the kernel a bit */
list = tracefs_event_systems(NULL);
tracefs_list_free(list);

upstream bug seems to have stalled with Adrien not replying. Someone
needs to pick that up, but I'm not the right person for that job.
upstream bug also mentions the s390x issues.

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to libtracefs in Ubuntu.
https://bugs.launchpad.net/bugs/2062119

Title:
  libtracefs autopkgtests fail on ppc64el

Status in The Ubuntu-power-systems project:
  Triaged
Status in libtracefs package in Ubuntu:
  Triaged

Bug description:
  As part of the added QA to libtracefs it was found that it triggers issues on ppc64el.
  It is not yet clear if those are just test artifacts or real deeper problems.

  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://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/ppc64el/libt/libtracefs/20240417_184416_c2b35@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2062119/+subscriptions