Ubuntu
libtracefs package

  1. Bug #2051925
  2. Comment #11

Comment 11 for bug 2051925

Revision history for this message
Adrien Nader (adrien) wrote :

I just got test results on amd64 and arm64.

https://autopkgtest.ubuntu.com/results/autopkgtest-noble-adrien-n-noble-libtracefs-mir/noble/amd64/libt/libtracefs/20240416_142558_e8175@/log.gz

https://autopkgtest.ubuntu.com/results/autopkgtest-noble-adrien-n-noble-libtracefs-mir/noble/arm64/libt/libtracefs/20240416_142825_fe233@/log.gz

As you see, it's not valgrind-clean but I don't think that matters as that's probably stuff that won't grow as usage grows and libtracefs is not meant to be used for long period of times at once.

i386 and armhf fail due to uninstallable dependencies due to issues not related to this MIR AFAICT; I don't think these platforms matter for libtracefs.

ppc64el failure: https://autopkgtest.ubuntu.com/results/autopkgtest-noble-adrien-n-noble-libtracefs-mir/noble/ppc64el/libt/libtracefs/20240416_140308_3a076@/log.gz

s390x failure: https://autopkgtest.ubuntu.com/results/autopkgtest-noble-adrien-n-noble-libtracefs-mir/noble/s390x/libt/libtracefs/20240416_140252_c405a@/log.gz