Open andyli opened 5 years ago
Looks like a random fail. At least it doesn't fail since then. Let's wait for a while and close the issue if it won't happen again.
I have no idea how something like that happens... but I agree that there's not much value in keeping the issue open as it didn't happen again.
This started to happen pretty often recently https://dev.azure.com/HaxeFoundation/GitHubPublic/_build/results?buildId=497&view=logs&jobId=d81420a3-bf30-5d37-575b-fa6a2af01070
I noticed that too... It almost looks like the jvm
package is not excluded somewhere, but I have no idea why this isn't deterministic.
This is probably not gonna be useful at all... but who knows:
On my fork I had a very similar issue on one of my commits (only for windows64-test (macro)
, everything else worked fine).
I thought the issue was weird so I reran the jobs, and consistently on that commit I would get the same error for that same test. Eventually I gave up, and after pushing a commit where all I did was fix inconsistent indentation in an ocaml file, suddenly the issue disappeared.
I got a slightly different output I think:
utest/ui/text/PrintReport.hx:52:
assertations: 1166
successes: 1165
errors: 1
failures: 0
warnings: 0
execution time: 24.601
results: SOME TESTS FAILURES (success: false)
cases.Issue5172
test: ERROR ...E
HaxeInvocationException(src/DisplayTestContext.hx:27: characters 26-36 : Unknown identifier : haxeserver
D:\a\haxec\haxec\win64Binaries\haxe_20210828031944_de8fbf6\std/haxe/macro/ExampleJSGenerator.hx:102: characters 12-17 : Class<haxe.macro.Context> has no field error
D:\a\haxec\haxec\win64Binaries\haxe_20210828031944_de8fbf6\std/sys/thread/Lock.hx:26: characters 8-52 : This class is not available on this target
, test, [--display,src/cases/Issue5172.hx@69@usage], package cases;
class Main {
static function main() {
for (i in 0...10) {
i;
}
}
}
])
Called from local function #1 (src/cases/Issue5172.hx line 13 column 2)
Called from cases.Issue5172.test (src/cases/Issue5172.hx line 17 column 26)
Called from DisplayTestContext.usage (src/DisplayTestContext.hx line 76 column 27)
Called from DisplayTestContext.callHaxe (src/DisplayTestContext.hx line 113 column 4)
Command exited with 1 in 26s: haxe [build.hxml]
test macro failed
Somehow the #5172 test started failing in CI.
Build log: