This bug was fixed in the package libtracefs - 1.8.0-1ubuntu1
---
libtracefs (1.8.0-1ubuntu1) noble; urgency=medium
* Remove "patches/" from .gitignore
* Bump libtraceevent-dev Build-Depends to >= 1:1.8.0
* Only use online CPUs during tests
-
This is a MIR requirement, see bug #2051925
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055309
Title:
No test suite run at built time nor as autopkgtest
To manage notifications about this bug
** Changed in: libtracefs (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055309
Title:
No test suite run at built time nor as autopkgtest
To manage
** Merge proposal linked:
https://code.launchpad.net/~adrien-n/ubuntu/+source/libtracefs/+git/libtracefs/+merge/464434
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055309
Title:
No test suite
** Changed in: libtracefs (Ubuntu)
Assignee: (unassigned) => Adrien Nader (adrien-n)
** Changed in: libtracefs (Ubuntu)
Status: New => In Progress
** Changed in: libtracefs (Ubuntu)
Milestone: None => ubuntu-24.04
--
You received this bug notification because you are a member
I carried this forward.
In a Noble LXD container, the test setup doesn't work.
In a Noble LXD VM, three tests fail: tracefs_iterate_snapshot_events, ,
and uprobes.
The first and second tests fail because they try to sched_setaffinity()
across 8 cores which the VM host has but the VM itself has
I spent some time investigating today the uprobes tests failure. I
understand these test fail because the call to tracefs_event_enable() in
check_probes returns -1. It also encounters errno=524, which is
(apparently) the err number returned by seccomp when failing to load a
filter. (see
I have a patch to run tests in autopkgtest but these tests are failing.
I checked and they are failing without any change on my side.
2 out of 36 tests are failing. I will try to diagnose these failures.
# sudo ./utest/trace-utest
CUnit - A unit testing framework for C - Version 2.1-3
