were behaving differently. Paride and I have tracked this down to a
change in systemd's behavior which results in the testbed exiting
abnormally. I've temporarily modified our autopkgtest code in
production so that this will not be considered a "testbed" failure which
will prevent packages with autopkgtests that are OOM killed from running
I mention it because the log files for tests in this situation have
changed and have become less informative. Looking the log file for
r-cran-rstanarm you'll see the following:
autopkgtest [18:46:11]: test run-unit-test: -----------------------]
autopkgtest [18:46:12]: test run-unit-test: - - - - - - - - - - results
- - - - - - - - - -
run-unit-test FAIL non-zero exit status 255
Which is less helpful than the previous "Killed signal terminated"
message. So when looking at proposed migration please keep this in mind.
Additionally, since we are talking about tests running out of memory I
wanted to mention that with the qemu backend it is possible to adjust
the amount of memory your virtual machine has using the "--ram-size"
argument. For example if I want to see if having more memory will allow
a test to pass I'll use the following before adding it to big_packages:
autopkgtest --apt-upgrade r-cran-rstanarm --shell-fail -- qemu
--ram-size=8192 --cpus=4 /srv/vms/autopkgtest-lunar-amd64.img
Finally, one benefit of this is that it became somewhat easier to find a
bunch of packages that would pass if given more memory. I've
investigated several of them and added them to 'big_packages'. If the
developers on +1 maintenance next week could look at the following list
it would be helpful!
 I've spoken with the Foundations team and they plan on uploading a
Have a great weekend!
ubuntu-devel mailing list
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel