<headius>
I went ahead and created a 3.2 branch that just bumps the compatibility version. This should help lavamind anewbhav and others start pushing some 3.2 features and tests
<headius>
lavamind: it's hard to get free 32-bit cloud instances these days so I would not be surprised if we have regressed on some things on 32-bit platforms
<headius>
testing all the platforms all the times is tricky
<lavamind[m]>
you should be able to run 32-bit images on 64-bit machines though?
<lavamind[m]>
I'm able to reproduce this specific problem on a i386 qemu VM locally
<headius>
build probably but if we can't test them does it help us
<lavamind[m]>
right, of course
<headius>
if you can file these I can at least test and fix them on the available instances
<lavamind[m]>
besides Debian I know OSUOSL does give access to CI runners on some less common platforms, let me find the info
<headius>
but maybe you were just asking if errors are expected... I say they are not surprising
<lavamind[m]>
ah yes, well that does help, that these errors are not totally unexpected
<lavamind[m]>
thanks for that
<headius>
there's one i386 machine on the gcc farm
<lavamind[m]>
I see GitHub doesn't offer a i386 image/runner
<lavamind[m]>
here's the OSUOSL link to request free hosting for aarch64 (there are also forms for ppc64el and s390x) https://osuosl.org/services/aarch64/
<lavamind[m]>
at Tor Project we use free GitLab runners that they provide us, very convenient