fix: correctly report error position on unknown directive without values #10088
Triggered via pull request
February 25, 2025 09:27
Status
Cancelled
Total duration
2h 30m 25s
Artifacts
33
ci.yml
on: pull_request
unit-tests
14m 5s
jvm-tests-1
1h 18m
jvm-tests-2
58m 33s
jvm-tests-3
1h 14m
jvm-tests-4
1h 1m
jvm-tests-5
1h 4m
checks
17m 27s
format
41s
reference-doc
2m 14s
vc-redist
0s
generate-linux-arm64-native-launcher
0s
generate-linux-launcher
9m 36s
generate-macos-m1-launcher
0s
generate-macos-launcher
14m 2s
generate-mostly-static-launcher
8m 6s
generate-static-launcher
8m 21s
generate-windows-launcher
10m 41s
docs-tests
39m 53s
bloop-memory-footprint
15m 20s
test-hypothetical-sbt-export
23s
native-linux-tests-1
34m 25s
native-linux-tests-2
29m 39s
native-linux-tests-3
34m 34s
native-linux-tests-4
26m 43s
native-linux-tests-5
27m 38s
native-macos-m1-tests-1
0s
native-macos-m1-tests-2
0s
native-macos-m1-tests-3
0s
native-macos-m1-tests-4
0s
native-macos-m1-tests-5
0s
native-macos-tests-1
0s
native-macos-tests-2
0s
native-macos-tests-3
0s
native-macos-tests-4
0s
native-macos-tests-5
0s
native-mostly-static-tests-1
43m 5s
native-mostly-static-tests-2
39m 8s
native-mostly-static-tests-3
41m 27s
native-mostly-static-tests-4
36m 1s
native-mostly-static-tests-5
33m 54s
native-static-tests-1
43m 54s
native-static-tests-2
38m 56s
native-static-tests-3
40m 43s
native-static-tests-4
34m 58s
native-static-tests-5
37m 35s
native-windows-tests-1
43m 7s
native-windows-tests-2
36m 49s
native-windows-tests-3
1h 3m
native-windows-tests-4
34m 7s
native-windows-tests-5
36m 1s
Annotations
62 errors and 30 warnings
native-linux-tests-4
Process completed with exit code 1.
|
native-linux-tests-5
Process completed with exit code 1.
|
native-linux-tests-2
Process completed with exit code 1.
|
native-mostly-static-tests-5
Process completed with exit code 1.
|
native-mostly-static-tests-4
Process completed with exit code 1.
|
native-static-tests-4
Process completed with exit code 1.
|
native-linux-tests-1
Process completed with exit code 1.
|
native-linux-tests-3
Process completed with exit code 1.
|
native-mostly-static-tests-2
Process completed with exit code 1.
|
native-static-tests-2
Process completed with exit code 1.
|
native-static-tests-5
Process completed with exit code 1.
|
native-windows-tests-2
Process completed with exit code 1.
|
native-mostly-static-tests-3
Process completed with exit code 1.
|
native-windows-tests-4
Process completed with exit code 1.
|
native-static-tests-3
Process completed with exit code 1.
|
native-mostly-static-tests-1
Process completed with exit code 1.
|
native-windows-tests-5
Process completed with exit code 1.
|
native-static-tests-1
Process completed with exit code 1.
|
native-windows-tests-1
Process completed with exit code 1.
|
jvm-tests-2
Process completed with exit code 1.
|
jvm-tests-4
Process completed with exit code 1.
|
jvm-tests-5
Process completed with exit code 1.
|
jvm-tests-3
Process completed with exit code 1.
|
native-windows-tests-3
Process completed with exit code 1.
|
jvm-tests-1
Process completed with exit code 1.
|
native-macos-tests-4
Canceling since a higher priority waiting request for 'refs/pull/3518/merge' exists
|
native-macos-tests-3
Canceling since a higher priority waiting request for 'refs/pull/3518/merge' exists
|
native-macos-tests-1
Canceling since a higher priority waiting request for 'refs/pull/3518/merge' exists
|
native-macos-tests-2
Canceling since a higher priority waiting request for 'refs/pull/3518/merge' exists
|
generate-macos-m1-launcher
Canceling since a higher priority waiting request for 'refs/pull/3518/merge' exists
|
native-macos-tests-5
Canceling since a higher priority waiting request for 'refs/pull/3518/merge' exists
|
scala.cli.integration.BspTests3Lts.invalid diagnostics at startup ► :
test-report.xml#L0
Failed test found in:
test-report.xml
Error:
ERROR:
|
scala.cli.integration.BspTests3NextRc.invalid diagnostics at startup ► :
test-report.xml#L0
Failed test found in:
test-report.xml
Error:
ERROR:
|
scala.cli.integration.BspTests213.invalid diagnostics at startup ► :
test-report.xml#L0
Failed test found in:
test-report.xml
Error:
ERROR:
|
scala.cli.integration.BspTests3NextRc.invalid diagnostics at startup ► :
test-report.xml#L0
Failed test found in:
test-report.xml
Error:
ERROR:
|
scala.cli.integration.BspTests3Lts.invalid diagnostics at startup ► :
test-report.xml#L0
Failed test found in:
test-report.xml
Error:
ERROR:
|
scala.cli.integration.BspTests3Lts.invalid diagnostics at startup ► :
test-report.xml#L0
Failed test found in:
test-report.xml
Error:
ERROR:
|
scala.cli.integration.BspTestsDefault.invalid diagnostics at startup ► :
test-report.xml#L0
Failed test found in:
test-report.xml
Error:
ERROR:
|
scala.cli.integration.BspTests212.invalid diagnostics at startup ► :
test-report.xml#L0
Failed test found in:
test-report.xml
Error:
ERROR:
|
scala.cli.integration.BspTests213.invalid diagnostics at startup ► :
test-report.xml#L0
Failed test found in:
test-report.xml
Error:
ERROR:
|
scala.cli.integration.BspTests213.invalid diagnostics at startup ► :
test-report.xml#L0
Failed test found in:
test-report.xml
Error:
ERROR:
|
scala.cli.integration.BspTests3NextRc.invalid diagnostics at startup ► :
test-report.xml#L0
Failed test found in:
test-report.xml
Error:
ERROR:
|
scala.cli.integration.BspTests213.invalid diagnostics at startup ► :
test-report.xml#L0
Failed test found in:
test-report.xml
Error:
ERROR:
|
scala.cli.integration.CompileTests213.i3389 ► :
test-report.xml#L0
Failed test found in:
test-report.xml
Error:
ERROR:
|
scala.cli.integration.CompileTests213.i3389-2 ► :
test-report.xml#L0
Failed test found in:
test-report.xml
Error:
ERROR:
|
scala.cli.integration.BspTests212.invalid diagnostics at startup ► :
test-report.xml#L0
Failed test found in:
test-report.xml
Error:
ERROR:
|
scala.cli.integration.BspTests3Lts.invalid diagnostics at startup ► :
test-report.xml#L0
Failed test found in:
test-report.xml
Error:
ERROR:
|
scala.cli.integration.CompileTests3Lts.i3389 ► :
test-report.xml#L0
Failed test found in:
test-report.xml
Error:
ERROR:
|
scala.cli.integration.CompileTests3Lts.i3389-2 ► :
test-report.xml#L0
Failed test found in:
test-report.xml
Error:
ERROR:
|
scala.cli.integration.BspTests212.invalid diagnostics at startup ► :
test-report.xml#L0
Failed test found in:
test-report.xml
Error:
ERROR:
|
scala.cli.integration.BspTestsDefault.invalid diagnostics at startup ► :
test-report.xml#L0
Failed test found in:
test-report.xml
Error:
ERROR:
|
scala.cli.integration.BspTests3NextRc.invalid diagnostics at startup ► :
test-report.xml#L0
Failed test found in:
test-report.xml
Error:
ERROR:
|
scala.cli.integration.CompileTests3NextRc.i3389 ► :
test-report.xml#L0
Failed test found in:
test-report.xml
Error:
ERROR:
|
scala.cli.integration.CompileTests3NextRc.i3389-2 ► :
test-report.xml#L0
Failed test found in:
test-report.xml
Error:
ERROR:
|
scala.cli.integration.BspTestsDefault.invalid diagnostics at startup ► :
test-report.xml#L0
Failed test found in:
test-report.xml
Error:
ERROR:
|
scala.cli.integration.BspTestsDefault.invalid diagnostics at startup ► :
test-report.xml#L0
Failed test found in:
test-report.xml
Error:
ERROR:
|
scala.cli.integration.CompileTestsDefault.i3389 ► :
test-report.xml#L0
Failed test found in:
test-report.xml
Error:
ERROR:
|
scala.cli.integration.CompileTestsDefault.i3389-2 ► :
test-report.xml#L0
Failed test found in:
test-report.xml
Error:
ERROR:
|
scala.cli.integration.BspTests213.invalid diagnostics at startup ► :
test-report.xml#L0
Failed test found in:
test-report.xml
Error:
ERROR:
|
scala.cli.integration.BspTests3Lts.invalid diagnostics at startup ► :
test-report.xml#L0
Failed test found in:
test-report.xml
Error:
ERROR:
|
scala.cli.integration.BspTests3NextRc.invalid diagnostics at startup ► :
test-report.xml#L0
Failed test found in:
test-report.xml
Error:
ERROR:
|
scala.cli.integration.BspTests212.invalid diagnostics at startup ► :
test-report.xml#L0
Failed test found in:
test-report.xml
Error:
ERROR:
|
format
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
test-hypothetical-sbt-export
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
reference-doc
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
generate-mostly-static-launcher
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
generate-static-launcher
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
generate-linux-launcher
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
unit-tests
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
bloop-memory-footprint
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
checks
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
docs-tests
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
native-linux-tests-4
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
native-linux-tests-5
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
native-linux-tests-2
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
native-mostly-static-tests-5
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
native-mostly-static-tests-4
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
native-static-tests-4
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
native-linux-tests-1
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
native-linux-tests-3
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
native-mostly-static-tests-2
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
native-static-tests-2
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
native-static-tests-5
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
native-mostly-static-tests-3
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
native-static-tests-3
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
native-mostly-static-tests-1
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
native-static-tests-1
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
jvm-tests-2
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
jvm-tests-4
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
jvm-tests-5
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
jvm-tests-3
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
jvm-tests-1
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
jvm-launchers
Expired
|
109 MB |
|
linux-launchers
Expired
|
137 MB |
|
macos-launchers
Expired
|
107 MB |
|
mostly-static-launchers
Expired
|
37.2 MB |
|
static-launchers
Expired
|
36.1 MB |
|
test-results-docs-tests
|
2.35 KB |
|
test-results-jvm-tests-1
|
26.2 KB |
|
test-results-jvm-tests-2
|
19.8 KB |
|
test-results-jvm-tests-3
|
27.2 KB |
|
test-results-jvm-tests-4
|
19.7 KB |
|
test-results-jvm-tests-5
|
20.3 KB |
|
test-results-linux-tests-1
|
26.1 KB |
|
test-results-linux-tests-2
|
19.7 KB |
|
test-results-linux-tests-3
|
27 KB |
|
test-results-linux-tests-4
|
19.6 KB |
|
test-results-linux-tests-5
|
20.2 KB |
|
test-results-native-mostly-static-tests-1
|
26.2 KB |
|
test-results-native-mostly-static-tests-2
|
19.7 KB |
|
test-results-native-mostly-static-tests-3
|
27.1 KB |
|
test-results-native-mostly-static-tests-4
|
19.7 KB |
|
test-results-native-mostly-static-tests-5
|
20.2 KB |
|
test-results-native-static-tests-1
|
26.2 KB |
|
test-results-native-static-tests-2
|
19.7 KB |
|
test-results-native-static-tests-3
|
27 KB |
|
test-results-native-static-tests-4
|
19.6 KB |
|
test-results-native-static-tests-5
|
20.2 KB |
|
test-results-unit-tests
|
13.8 KB |
|
test-results-windows-tests-1
|
24.5 KB |
|
test-results-windows-tests-2
|
18.5 KB |
|
test-results-windows-tests-3
|
26.6 KB |
|
test-results-windows-tests-4
|
19 KB |
|
test-results-windows-tests-5
|
19.3 KB |
|
windows-launchers
Expired
|
108 MB |
|