What Git revision are you using?

aiken v1.1.21+42babe5

What operating system are you using, and which version?

• Linux / Ubuntu
• Linux / Other
• macOS
• Windows

Describe what the problem is?

The newly introduced expect traces should be correctly filtered using the [--trace-filter] option of the aiken build command.
Right now, they're understood as compiler-generated, however I believe they should rather be understood as user-defined

Also, there's no difference in the prefix when [--trace-level] being either verbose or compact; these expect prefixes are still the same, i.e. having the <expected> prefix. It's fine for verbose option, but for the compact option, there should be no prefix just the trace itself.

What should be the expected behavior?

Having the following code:

/// Something
expect False

1. command aiken build --trace-level verbose yields trace <expected> Something
2. [CHANGED] command aiken build --trace-level compact yields trace Something
3. [CHANGED] command aiken build --trace-level verbose --trace-filter user-defined yields trace <expected> Something
4. [CHANGED] command aiken build --trace-level compact --trace-filter user-defined yields trace Something
5. [CHANGED] command aiken build --trace-level verbose --trace-filter compiler-generated yields trace expect False
6. [CHANGED] command aiken build --trace-level compact --trace-filter compiler-generated yields I guess the line number? Not sure what was the previous behaviour