There are lots of mainline reports about this test, see links. For Leyden, there is additional specifics: we print advanced compile task information in compile log, so we get indenting/format mismatches.

Leyden dumps this:

```
     57 W0.0 Q0.0 C0.7 3 b compiler.inlining.LateInlinePrinting$TestLateInlining::test2 (7 bytes)
                            @ 0 compiler.inlining.LateInlinePrinting$TestLateInlining::test3 (1 bytes) inline (hot) late inline succeeded
                            @ 3 compiler.inlining.LateInlinePrinting$TestLateInlining::testFailInline (1 bytes) failed to inline: disallowed by CompileCommand
                            @ 6 compiler.inlining.LateInlinePrinting$TestLateInlining::testFailInline (1 bytes) failed to inline: disallowed by CompileCommand
                            @ 9 compiler.inlining.LateInlinePrinting$TestLateInlining::test2 (7 bytes) inline (hot) late inline succeeded
                              @ 0 compiler.inlining.LateInlinePrinting$TestLateInlining::inlined1 (1 bytes) inline (hot) late inline succeeded
                              @ 3 compiler.inlining.LateInlinePrinting$TestLateInlining::inlined2 (1 bytes) inline (hot) late inline succeeded
     58 W0.0 Q0.0 C1.1 4 b compiler.inlining.LateInlinePrinting$TestLateInlining::test1 (13 bytes)
```

So, this bug fixes the test for Leyden specifically, while mainline is figuring out the rest.