See JDK-8349915 for the example that should have been caught by CTW itself. Compilation policy may decide to compile on the different level, not the one CTW requested. This limits the scope of CTW testing, and likely hides bugs.

There are a few "normal" compilation level changes due to compiler bailouts, like:

```
[2] jdk.test.lib.Asserts::assertTrue(boolean) WARNING compilation level = 0, but not 1
```

These report "level 0" as the result, so we likely want to accept those. But the rest should probably be turned into fatal CTW failures to capture accidents like JDK-8349915.