E50320: probe output mismatch
What went wrong
A @Probe directive expected specific output but the actual probe output differs. This typically happens when IR or code generation changes affect the output captured by the probe.
Note
This code concerns a compiler-development directive. The directives other than @Test (the ones that state what the compiler should report, resolve, measure or generate for a source) are tooling for the people who develop the EK9 compiler; they are not designed for mainstream programs, and a program needs none of them. The only directive an EK9 program uses is @Test.
How to fix it
If you are writing an EK9 program: remove the directive. Only @Test belongs in a program. If you are developing the compiler: docs/testing/EK9_DIRECTIVE_TEST_FILE_PROCESS.md in the compiler repository describes every directive and how to fix this report.
Compiler development
This code concerns the compiler-development directives (@Error, @Resolved, @Complexity and the rest), which are not designed for mainstream programs - the only directive a program uses is @Test, so it has no example. Compiler developers: docs/testing/EK9_DIRECTIVE_TEST_FILE_PROCESS.md in the compiler repository describes every directive.