Following on from Help wanted to debug a segfault in a standard library test on Android, we're still seeing regular failures in CI due to this issue and it appears to be significantly worse on GitHub Actions (which we're evaluating at the moment).
We see three options, in order of desirability:
- the issue is fixed
- we disable should_panic tests on android
- we disable Android tests entirely (note that Android is a tier 2 platform so 'shouldn't' be getting testing anyway!)
The current status of things is:
- the infra team is extremely unlikely to be able to pursue option 1 or 2, hence 3 is the default (as sad as it is)
- the issue appears to be related to should_panic tests (hence option 2 above)
- to disable should_panic tests, we don't want to scatter cfgs everywhere, so two things need to happen:
- https://github.com/rust-lang/rust/pull/58900 shows roughly what needs to happen to disable normal should_panic tests (though that specific PR didn't work so may be misleading )
- rustdoc needs altering to allow us to pass a flag to disable should_panic doctests
The timeline for this is around a month - at that point we're expecting to make the final decision on GitHub Actions, which acts as a motivation to solve this issue one way or another.