-
Notifications
You must be signed in to change notification settings - Fork 27
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
Unit test failures #262
Comments
I don't have a test environment with latest haxe set up, so I only took a quick look at the tests: I'll see if I can setup a virtual machine to take a closer look. |
@Gama11: Could this be related to the |
That would definitely cause some failures, yes... Try replacing it with
|
Yes that helps:
These look like some $-parsing issue in haxeparser, I'll check it out. |
For what it's worth, I get 0 test failures on latest Haxe / checkstyle, but on HaxeCheckstyle/haxeparser@6776c7b. |
Yes I know I broke it when I implemented HaxeCheckstyle/haxeparser@5b0bf9f, I'm just not sure why yet. This stuff is pretty meta... |
What's the status here? |
This allows having a version check in haxe-checkstyle to deal with #30 (see also HaxeCheckstyle/haxe-checkstyle#262).
There's still some failing tests (see #262 and HaxeCheckstyle/haxeparser#36), but I think it's better to ignore those for now than to not test against latest Haxe and haxeparser at all.
probably fixed a long time ago. |
I've just tried running the unit tests with latest Haxe and haxeparser and got some failures. I would like to understand why these happens and if they indicate regressions from either Haxe or haxeparser:
I'll take a closer look tomorrow but if someone wants to take a look as well that would be appreciated.
The text was updated successfully, but these errors were encountered: