@dmitshur I'm in the process of provisioning two new builders and the issue came up when testing them. I stopped the new builders as soon as I saw the failure so that's why its not currently happening.
The current builders are not triggering this issue probably because they are on an older RHEL version (8.2) and the new builders are on the latest RHEL 8.5 version. I haven't been able to track down the exactly what selinux configuration causes the difference but I don't think there is any misconfiguration of the new builders. I think I was just unlucky enough to hit another valid selinux configuration that wasn't yet covered by the expected values in the test.
The failure is definitely deterministic and to the best of my understanding not platform dependent in any way.
“If you have a procedure with ten parameters, you probably missed some.”
― attr. Alan J. Perlis
I argue that the same is true for hard-coded special cases.
In TestGroupCleanupUserNamespace, instead of a curated list of strings
observed in the wild we now check for a prefix, as was done for
TestGroupCleanup in CL 24670.
Trust: Bryan Mills <email@example.com>
Run-TryBot: Bryan Mills <firstname.lastname@example.org>
TryBot-Result: Gopher Robot <email@example.com>
Reviewed-by: Ian Lance Taylor <firstname.lastname@example.org>
(cherry picked from commit 434b2a5)
Reviewed-by: Russ Cox <email@example.com>