Bug#1069600: Fwd: dm-writeboost: isolation-machine autopkgtest fails: sudo: not found

2024-05-05 Thread Andreas Beckmann

On 06/05/2024 07.38, Paul Gevers wrote:

Hi,

On 05-05-2024 8:04 p.m., Andreas Beckmann wrote:
167s autopkgtest [09:50:25]: test test-dm-writeboost.sh: 
[---

168s II: Checking for 14G available disk space...SKIP


How much disk space is used already by the time you get to this test? 


The test has done nothing, yet.

The root of the testbed has 25 GB total (starting off with 990 MB used), 
so your test has 24 GB to use (including installing test dependencies).


The biggest test dependency is (virtual) linux-headers-generic + deps, 
as (virtual) linux-image-generic should already be isntalled ...


So there should be plenty of space available.

The skip is probably coming from the non-verbose check for 8 CPUs where 
I applied the patch from Ubuntu... Will make that verbose and also 
report skip reasons better.


Andreas



Bug#1069600: Fwd: dm-writeboost: isolation-machine autopkgtest fails: sudo: not found

2024-05-05 Thread Paul Gevers

Hi,

On 05-05-2024 8:04 p.m., Andreas Beckmann wrote:
167s autopkgtest [09:50:25]: test test-dm-writeboost.sh: 
[---

168s II: Checking for 14G available disk space...SKIP


How much disk space is used already by the time you get to this test? 
The root of the testbed has 25 GB total (starting off with 990 MB used), 
so your test has 24 GB to use (including installing test dependencies).


Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1069600: Fwd: dm-writeboost: isolation-machine autopkgtest fails: sudo: not found

2024-05-05 Thread Andreas Beckmann

On 28/04/2024 11.35, Paul Gevers wrote:

Hi,

On 28-04-2024 9:34 a.m., Andreas Beckmann wrote:
What kernel is running inside the test environment and what is the 
best way to install its headers?


Can you help me find the answer? I guess you don't mean "the current 
kernel of the suite under test" but rather a flavor? We use 
autopkgtest-build-qemu, which uses vmdb2, to build the image. The kernel 
used is also logged in the autopkgtest log, so you can also look it up :).


That was too trivial. I expected you had done something fancy (and 
completely different from the normal test runs) to enable 
isolation-machine ;-) (And while reading the log I didn't spot anything 
interesting to answer my questions. But I didn't look outside the 
sections of that specific test.)



Would Depends: linux-headers-generic work?


I don't know.


It does. If its spelled correctly ;-)

The corresponding changes for the autopkgtest are now in sid. Including 
a change from Ubuntu to skip the test on low powered systems.
There has been migration test run on amd64 already and the new test got 
skipped:


167s autopkgtest [09:50:25]: test test-dm-writeboost.sh: 
[---

168s II: Checking for 14G available disk space...SKIP
168s autopkgtest [09:50:26]: test test-dm-writeboost.sh: 
---]


The next check would have been for 8+ cpu cores.

So, yes, isolation-machine works^Wdoesn't fail for dm-writeboost but it 
is not helpful for this package since it cannot provide the required 
resources.




Andreas



Bug#1069600: Fwd: dm-writeboost: isolation-machine autopkgtest fails: sudo: not found

2024-04-28 Thread Paul Gevers

Hi,

On 28-04-2024 9:34 a.m., Andreas Beckmann wrote:
What kernel is running inside the test environment and what is the best 
way to install its headers?


Can you help me find the answer? I guess you don't mean "the current 
kernel of the suite under test" but rather a flavor? We use 
autopkgtest-build-qemu, which uses vmdb2, to build the image. The kernel 
used is also logged in the autopkgtest log, so you can also look it up :).



Would Depends: linux-headers-generic work?


I don't know.


Or better in the test script to
   test -d /lib/modules/$(uname -r)/build || \
   apt-get install linux-headers-$(uname -r)


But I have a strong preference for (test) Depends over running $(apt-get 
install) inside the test for two reasons:
1) you get Autopkgtest-Triggers for the kernel (headers) for free, 
meaning that we'll know if the kernel breaks this package
2) the autopkgtest setup for migration is a bit weird and getting it 
right shouldn't be the responsibility of the test [1].


Paul

[1] 
https://wiki.debian.org/ContinuousIntegration/AutopkgtestBestPractices 
(under "Don't").


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1069600: Fwd: dm-writeboost: isolation-machine autopkgtest fails: sudo: not found

2024-04-28 Thread Andreas Beckmann

On 22/04/2024 19.46, Paul Gevers wrote:

you. In case you are not subscribed, this message again.


Thanks. Please keep me Cc:ed.

For this concrete case it may be as simple as adding dependency on 
sudo. In case it is trivial for you to rerun the failing test with


Thanks for running the test.

II: Loading dm-writeboost module...modprobe: FATAL: Module dm-writeboost 
not found in directory /lib/modules/6.6.15-amd64

FAILED!


OK, one step further. No module was built because no headers are 
installed ;-)


What kernel is running inside the test environment and what is the best 
way to install its headers?


Would Depends: linux-headers-generic work?
Or better in the test script to
  test -d /lib/modules/$(uname -r)/build || \
  apt-get install linux-headers-$(uname -r)


Andreas