Comment 1 for bug 1949801

There is one odd issue (bug #1951289) where one CPU seems unable to schedule across all possible CPUs. However this could not be seen on other arm64 hardware. For that I am tempted to say this is either a hardware issue or race. However this happening on a CPU #32 when 128 are available sounds a little suspicious.

The remaining missing results are deploy or setup issues on nodes which are extremely slow/busy (spitfire/michael).