HaxeFoundation / haxe

Haxe - The Cross-Platform Toolkit
https://haxe.org
6.17k stars 655 forks source link

Test fails on the Windows64 target (macro) #11756

Closed SomeGuyWhoLovesCoding closed 2 weeks ago

SomeGuyWhoLovesCoding commented 2 months ago

So here, this is the error log:

Command exited with 0 in 2s: haxelib [git,haxeserver,https://github.com/Simn/haxeserver]
Command: haxe [build.hxml,-D,display.protocol=xml]
utest/ui/text/PrintReport.hx:52: 
assertations: 1246
successes: 1244
errors: 2
failures: 0
warnings: 0
execution time: 13.293

results: SOME TESTS FAILURES (success: false)
cases.Issue5172
  test: ERROR ...E
    HaxeInvocationException(D:\a\haxe\haxe\win[64](https://github.com/HaxeFoundation/haxe/actions/runs/10659996047/job/29543872222?pr=11750#step:13:65)Binaries\haxe_20240902030117_70c3cde\std/haxe/macro/ExampleJSGenerator.hx:102: characters 12-17 : Class<haxe.macro.Context> has no field error
src/XmlDisplayTestCase.hx:2: characters 8-20 : Type not found : utest.Assert
src/RpcDisplayTestCase.hx:3: characters 8-20 : Type not found : utest.Assert
D:\a\haxe\haxe\win64Binaries\haxe_20240902030117_70c3cde\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 XmlDisplayTestContext.usage (src/XmlDisplayTestContext.hx line 37 column 27)
Called from XmlDisplayTestContext.callHaxe (src/XmlDisplayTestContext.hx line [65](https://github.com/HaxeFoundation/haxe/actions/runs/10659996047/job/29543872222?pr=11750#step:13:66) column 4)
cases.Issue6405
  test: ERROR .E
    HaxeInvocationException(D:\a\haxe\haxe\win64Binaries\haxe_20240902030117_70c3cde\std/haxe/macro/ExampleJSGenerator.hx:102: characters 12-17 : Class<haxe.macro.Context> has no field error
src/XmlDisplayTestCase.hx:2: characters 8-20 : Type not found : utest.Assert
D:\a\haxe\haxe\win64Binaries\haxe_20240902030117_[70](https://github.com/HaxeFoundation/haxe/actions/runs/10659996047/job/29543872222?pr=11750#step:13:71)c3cde\std/sys/thread/Lock.hx:26: characters 8-52 : This class is not available on this target

, test, [--display,src/cases/Issue6405.hx@165@usage], package cases;

        import haxe.macro.Expr;
        import haxe.macro.Context;
        using haxe.macro.ExprTools;

        class Macros {

            public static macro function makeTypeDef( e : Expr ) {
                var t = Context.getType(e.toString());
                return macro {};
            }

        }
    ])
Called from local function #1 (src/cases/Issue6405.hx line 18 column 2)
Called from cases.Issue6405.test (src/cases/Issue6405.hx line 20 column 15)
Called from XmlDisplayTestContext.usage (src/XmlDisplayTestContext.hx line 37 column 27)
Called from XmlDisplayTestContext.callHaxe (src/XmlDisplayTestContext.hx line 65 column 4)

Command exited with 1 in 14s: haxe [build.hxml,-D,display.protocol=xml]
 WARNING  D:\a\haxe\haxe\tests\unit\src\unit\TestGADT.hx

   | (WUnboundTypeParameter) Unbound type parameter EBinop.C

 WARNING  D:\a\haxe\haxe\tests\unit\src\unit\issues\Issue11513.hx

   | (WUnboundTypeParameter) Unbound type parameter send.TBody

test macro failed
Error: Process completed with exit code 1.

Which tells me that some tests failed on the 64 bit windows target on macro. I would really love that to be fixed please.

          I gotta make an issue about that

Originally posted by @SomeGuyWhoLovesCoding in https://github.com/HaxeFoundation/haxe/issues/11750#issuecomment-2323744809

SomeGuyWhoLovesCoding commented 2 months ago

Starts here: https://github.com/HaxeFoundation/haxe/actions/runs/10659996047/job/29543872222?pr=11750#step:13:57

Simn commented 2 months ago

Yeah this has been randomly failing for a while and nobody knows why. It keeps failing if you restart the test, but then on the next commit it suddenly works.

SomeGuyWhoLovesCoding commented 2 months ago

Lmao that never happened to me before but I would love someone to figure out that issue.

Simn commented 2 weeks ago

I've closed this as unresolved before and I'll do so again. Maybe one day someone will figure out what's going on.