Comment 5 for bug 1822246

This may be unrelated however the failure is also found on disco, 5.0 kernel. The actual failure messages themselves are the same, this is on the AWS Cloud, across all instance types.
This relatively new test was added back in Feb.

https://patchwork.ozlabs.org/patch/1048709/

10/01 18:59:01 DEBUG| utils:0153| [stdout] tag=binfmt_misc01 stime=1569956330 dur=0 exit=exited stat=0 core=no cu=6 cs=1
10/01 18:59:01 DEBUG| utils:0153| [stdout] startup='Tue Oct 1 18:58:56 2019'
10/01 18:59:01 DEBUG| utils:0153| [stdout] binfmt_misc02 1 TINFO: timeout per run is 0h 5m 0s
10/01 18:59:01 DEBUG| utils:0153| [stdout] binfmt_misc02 1 TFAIL: Recognise a disabled binary type successfully
10/01 18:59:01 DEBUG| utils:0153| [stdout] binfmt_misc02 2 TFAIL: Recognise a disabled binary type successfully
10/01 18:59:01 DEBUG| utils:0153| [stdout] binfmt_misc02 3 TFAIL: Recognise a disabled binary type successfully
10/01 18:59:01 DEBUG| utils:0153| [stdout] binfmt_misc02 4 TFAIL: Recognise a disabled binary type successfully
10/01 18:59:01 DEBUG| utils:0153| [stdout] binfmt_misc02 5 TFAIL: Recognise a binary type successfully
10/01 18:59:01 DEBUG| utils:0153| [stdout] binfmt_misc02 6 TFAIL: Recognise a binary type successfully
10/01 18:59:01 DEBUG| utils:0153| [stdout] binfmt_misc02 7 TINFO: AppArmor enabled, this may affect test results
10/01 18:59:01 DEBUG| utils:0153| [stdout] binfmt_misc02 7 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root)
10/01 18:59:01 DEBUG| utils:0153| [stdout] binfmt_misc02 7 TINFO: loaded AppArmor profiles: modprobe