Andreas Hasenack

I'm seeing this crash in all architectures in ubuntu: https://autopkgtest.ubuntu.com/packages/g/glusterfs/mantic/amd64 https://autopkgtest.ubuntu.com/packages/g/glusterfs/mantic/arm64 https://autopkgtest.ubuntu.com/packages/g/glusterfs/mantic/ppc64el https://autopkgtest.ubuntu.com/packages/g/glusterfs/mantic/s390x

I'm seeing the same issue on two 22.10 ubuntu systems, I opened a thread in discourse: https://discuss.kubernetes.io/t/error-enabling-metallb-internal-error-context-deadline-exceeded/22092/

I repeated my same steps on an Ubuntu 22.04 LTS install, and this time it all worked. More specifically, I retried a simpler case in VMs first, without involving `metallb`,...

> and see if failurePolicy is set to Fail, I believe you can set it to ignore. It's `Fail` indeed, but before ignoring an error it's important to understand why...

Debian is patching this package a bit, and if I remove this hunk from this patch file, then there is no segfault, hmm... https://salsa.debian.org/ruby-team/ruby-ferret/blob/master/debian/patches/disable_load_path_manipulation.patch#L18

I tried moving the lock to the beginning of the test, but then another type of error showed up. The other thing I tried was to run the tests with...

I tried bumping that sleep to 10s, but it still fails in multiple runs. We can see a 10s delay in between some of this test output: ``` 1590s Finished...