Re: +1 maintenance report (14/Aug - 18/Aug)
On Mon, Aug 21, 2023 at 02:28:50PM -0700, Bryce Harrington wrote: > > The armhf lxd containers do not have hard partitioning of memory > > allocations, so *generally* tests on armhf will have more memory available > > than on other architectures. But that memory is also shared across tests, > > so "noisy neighbor" effect is more of a problem. > Is there a technique for identifying when this may be the case, when > we're troubleshooting armhf-specific issues? If it looks like an OOM error only on armhf, retry it and see if it's reproducible. > You know, it would be super useful if we had a handbook of architectures > for our autopkgtest infrastructure, that explains both the fundamental > differences between the architectures (e.g. cpu-specific uniquenesses) > and the implementational characteristics of how it's set up in Canonical > infrastructure (e.g. the memory configuration strategy with the armhf > lxd containers). Does a doc like this already exist? https://wiki.debian.org/ArchitectureSpecificsMemo is a good overview of architecture differences, which also applies to Ubuntu. It might be a good starting point for someone to create a doc that distills this for just the Ubuntu architectures. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: +1 maintenance report (14/Aug - 18/Aug)
On Mon, Aug 21, 2023 at 09:47:18AM -0700, Steve Langasek wrote: > On Mon, Aug 21, 2023 at 10:16:31AM +0800, Shengjing Zhu wrote: > > + golang-github-protonmail-go-crypto > > The error message says "out of memory". I can reproduce this on a VM with > > 500M memory. > > It's because the testdata in TestSymmetricDecryptionArgon2 uses a large > > memory exponent parameter. > > It's same as https://github.com/ProtonMail/go-crypto/pull/178 (But this > > bug is only for 32bit arch, and is fixed in this package). > > TestSymmetricDecryptionArgon2 is passed on 32bit arch, but only fails on > > arm64 and s390x. Maybe the autopkgtest VM for these two architectures > > has less memory? even less than armhf (I know it is lxd container > > instead VM, but not sure about the memory configurations). > > > LP: #2032145 > > The armhf lxd containers do not have hard partitioning of memory > allocations, so *generally* tests on armhf will have more memory available > than on other architectures. But that memory is also shared across tests, > so "noisy neighbor" effect is more of a problem. Is there a technique for identifying when this may be the case, when we're troubleshooting armhf-specific issues? You know, it would be super useful if we had a handbook of architectures for our autopkgtest infrastructure, that explains both the fundamental differences between the architectures (e.g. cpu-specific uniquenesses) and the implementational characteristics of how it's set up in Canonical infrastructure (e.g. the memory configuration strategy with the armhf lxd containers). Does a doc like this already exist? For new +1 maintainers this might help with some of the sense of overwhelm one gets, but also even for experienced folks having itemized lists of idiosyncrasies could help jog the memory. (And as the infrastructure evolves it could help communicate what's changed, and/or identify more ways to improve...) Bryce -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: +1 maintenance report (14/Aug - 18/Aug)
On Mon, Aug 21, 2023 at 10:16:31AM +0800, Shengjing Zhu wrote: > + golang-github-protonmail-go-crypto > The error message says "out of memory". I can reproduce this on a VM with > 500M memory. > It's because the testdata in TestSymmetricDecryptionArgon2 uses a large > memory exponent parameter. > It's same as https://github.com/ProtonMail/go-crypto/pull/178 (But this > bug is only for 32bit arch, and is fixed in this package). > TestSymmetricDecryptionArgon2 is passed on 32bit arch, but only fails on > arm64 and s390x. Maybe the autopkgtest VM for these two architectures > has less memory? even less than armhf (I know it is lxd container > instead VM, but not sure about the memory configurations). > LP: #2032145 The armhf lxd containers do not have hard partitioning of memory allocations, so *generally* tests on armhf will have more memory available than on other architectures. But that memory is also shared across tests, so "noisy neighbor" effect is more of a problem. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
+1 maintenance report (14/Aug - 18/Aug)
Hi,
+ go-exploitdb
Blocks the migration of golang-gopkg-cheggaaa-pb.v1.
Upload 0.0~git20181130.7c961e7-3 and request sync LP: #2031610
+ gost
Blocks the migration of golang-gopkg-cheggaaa-pb.v1.
Upload 0.1.2-2 and request sync LP: #2031609
+ golang-github-labstack-echo
autopkgtest fails due to http_proxy env and png file in testdata is mangled.
Upload 4.11.1-2
+ golang-github-form3tech-oss-jwt-go
- Upload goval-dictionary and go-cve-dictionary to get rid of
golang-github-labstack-echo.{v2,v3} and golang-github-dgrijalva-jwt-go
- File RM request for golang-github-labstack-echo.{v2, v3}
Debian Bug #1049945, #1049946
+ golang-github-mdlayher-socket
Test only fails on launchpad. Narrow down to the kernel version from focal.
Upload 0.4.1-2
+ golang-github-protonmail-go-crypto
The error message says "out of memory". I can reproduce this on a VM with
500M memory.
It's because the testdata in TestSymmetricDecryptionArgon2 uses a large
memory exponent parameter.
It's same as https://github.com/ProtonMail/go-crypto/pull/178 (But this bug
is only for 32bit arch, and is fixed in this package).
TestSymmetricDecryptionArgon2 is passed on 32bit arch, but only fails on
arm64 and s390x. Maybe the autopkgtest VM for these two architectures has
less memory? even less than armhf (I know it is lxd container instead VM, but
not sure about the memory configurations).
LP: #2032145
+ petsc4py
I got trouble and wasted some time to reproduce the autopkgtest errors in
local at first. It turns out to blame my autopkgtest docker images. Sign...
I use autopkgtest-virt-docker and build the image from the ubuntu:mantic base
image. But, it contains a /etc/dpkg/dpkg.cfg.d/excludes file that excludes all
/usr/share/doc/* files!
So my local reproduce for petsc4py's run-demo test always fails with "No rule
to make target 'all'" (What happens, where is the makefile??)
The autopkgtest failure is caused by `-Wl,-z,defs` added in
petsc/3.18.6+dfsg1-1ubuntu1.
The intention for `-Wl,-z,defs` looks good. But I still haven't find where to
inject missing libraries in petsc4py's autopkgtest.
Test code is in ./demo/wrap-swig/ dir, and it will reuses petsc's build
configurations, and is located at /usr/lib/petsc64/lib/petsc/conf/, and is
influenced by the flags that are set in build time.
LP: #2032144
--
Shengjing Zhu
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
