the test being killed, and realized that people might see confusing test
behavior when looking at the results of specific packages.
For example with the recent rust-pyo3 results for ppc64el on oracular[1]
we can see the tests switching from pass, to fail and then a pass again.
This is[2] due to the data center in which test tests are running.
We are currently in the process of moving ppc64el and s390x tests from
scalingstack to ProdStack6. As a part of the move we have increased
the number of processors and memory available to the autopkgtest
(default) flavor used for running tests in ProdStack6. So an instance
running an autopkgtest will currently have more resources depending on
which data center it is provisioned in. The distinction you'd want to
look for in the log files are bos01/bos2 (scalingstack) and bos03 (PS6)
e.g.
autopkgtest-juju-7f2275-prod-proposed-migration-environment-2@bos02-ppc64el-11.secgroup
If you see a test passing in bos03 but not in bos01 or bos02 the package
might need adding to big_packages[3].
[1] https://autopkgtest.ubuntu.com/packages/rust-pyo3/oracular/ppc64el
[2] Well was - I added the package to big_packages to get consistent
results.
[3]
https://git.launchpad.net/~ubuntu-release/autopkgtest-cloud/+git/autopkgtest-package-configs/
Have a great weekend!
--
Brian Murray
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
