Comment 3 for bug 1945713

I spent some time trying to get to the bottom of the issue, but unfortunately I was not able to make much progress here.

As expected, the very first thing to do here is to reproduce the bug locally. I tried many things:

- I built the package locally and ran autopkgtest against it. Passed.

- I built the package inside a Focal LXD container and then ran autopkgtest there. Passed.

- Still inside the Focal LXD container, I tried to invoke the failing test manually. Passed.

- I know that Ubuntu's autopkgtest infra uses a Bionic host to run the tests. I created a Bionic VM, and inside it I git cloned the development version of autopkgtest. Then, I invoked autopkgtest against the Focal source package for libsoup2.4, using a Focal LXD container as the testbed. Passed.

I ran out of ideas on what to try locally, and given that Bryce was able to add a hint for the failure and unblock apache2, I am giving up (at least for now). The way I see it, a person interested in continuing debugging this could:

- Add debugging statements to the libsoup2.4 code, upload the modified package to a PPA, and run autopkgtests using the Ubuntu infra. This should be able to provide more useful information regarding the array manipulation that's happening in the test.

- If the above doesn't work, one could try to add debugging statements to the libglib code that's responsible for array manipulations.

Lastly, it's important to mention that this may very well be something unrelated to libsoup2.4/glib. It can even be a hardware issue, who knows...