-
-
Notifications
You must be signed in to change notification settings - Fork 662
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Static Extension failing in nightly builds (Flixel CI error) #11353
Comments
Sounds like a problem with the coverage macro. Where is it from? |
Would be good to know which change broke this. It's probably module resolution, but static extensions shouldn't really be affected by it much, so I'm a bit curious. |
I suspect the error position is not the actual position, but a macro using that position and using some "deprecated" module resolution |
I see this in BOTH the earliest failing and latest succeeding CI jobs:
Earlier jobs have a different value. I assumed this would be some commit hash but the fact that it appears in both failing and succeeding jobs makes me think that perhaps this started happening when I changed a secondary flixel repo, like flixel-ui or flixel-addons, or maybe a change to lime or openfl. |
coverage "macro"? I don't understand, I link the coverage test's project.xml in the original post, if that helps |
That project uses |
That was more directed towards @kLabz' "what macro" question. |
Yeah I expected some macro doing "real coverage" instead of an "import all" thing. |
The
With
I don't know why that's the case and what it means. |
And yes I confirm that this was caused by #11168. |
Fixed by #11388. |
Flixel CI has been failing nightly builds as of late:
the issue is that the static extender class, FlxColorTransformUtil seems to be ignored, despite being used
Note this only happens in the coverage test with coverage2 enabled which is defined here, it simply enables debug mode
It's hard to create a more simplified repro, but if there's anything else you need, I will try
The text was updated successfully, but these errors were encountered: