Update test target to current Ubuntu

[wiredfool]

No description provided.

[radarhere]

Not quite related question - when I run this branch in my own fork, it fails, saying that it is "Unable to find image 'githubactions/ubuntu-22.04-jammy-amd64:main' locally" (whereas main passes).

Any ideas why that might be?

[wiredfool]

There's a race condition between this image and the test image -- if we're not on main and there isn't a version of it pushed to dockerhub. Because of the branch and username, we're specifically using the test version that's built in this (or your) pr. It might get better on subsequent runs if it's actually pushing to dockerhub, or it won't.

[hugovk]

Should this target Python 3.11 by default?

[wiredfool]

No, because Jammy doesn't.

[wiredfool]

guess I'm backing up the CI queue today.

[hugovk]

This should help: #162

[wiredfool]

Now I'm just feeling bad for the CO2 burned:

Why is this attempting to run 8 times?

[radarhere]

I don't know where that screenshot comes from, but I really don't think that all of the jobs ran 8 times - I expect it was only one of them that had 8 attempts.

Our test suite has some intermittent failures, but the main culprit is test_redos in test_file_pdf.py. It has a timeout that tends to fail on the slower valgrind job. I tend to rerun the failing job until it passes.