Jaroslav Tulach 9134f9b2d7 EnsoCompilerTest to verify compatibility of parsers (#3723) ... Adding new _compatibility test_ `EnsoCompilerTest` to verify the new Rust based parser can produce the same `IR` as the original `AST` based one. The simplest way to execute the test from an empty repository is: ```bash enso$ sbt bootstrap enso$ sbt "testOnly *EnsoCompilerTest" ``` There are [GitHub Actions run](https://github.com/enso-org/enso/actions/runs/3087664644/jobs/4993266212#step:9:5187) on Linux as well as [run on Windows](https://github.com/enso-org/enso/actions/runs/3087664644/jobs/4993266370#step:9:5254) that show `EnsoCompilerTest` is being executed by the CI (good, as that means `.so` was properly built and linked to the JVM running the test). The [linux](https://github.com/enso-org/enso/actions/runs/3087664644/jobs/4993266212#step:9:5187) as well as [windows](https://github.com/enso-org/enso/actions/runs/3087664644/jobs/4993266370#step:9:5254) runs also demonstrate that failures in the `EnsoCompilerTest` suite fail the CI. # Important Notes Right now [there are five test failures](https://github.com/enso-org/enso/actions/runs/3087664644/jobs/4993266212#step:9:5187) - waiting for @kazcw to make sure `codeRepr()` doesn't contain spaces. However, as this PR is more about the infrastructure, I am disabling the currently failing tests in [031169b](031169bd05)		2022-09-20 15:50:27 +00:00
..
generate-java	EnsoCompilerTest to verify compatibility of parsers (#3723)	2022-09-20 15:50:27 +00:00
jni	Parser: Parse UUIDs; implement comments in AST; implement type annotations and signatures; fix field names (#3653)	2022-09-03 03:15:27 +00:00
src	Parser: Named and default arguments; Text interpolation; Escape sequences (#3709)	2022-09-14 22:32:28 -07:00
tests	Parser: Named and default arguments; Text interpolation; Escape sequences (#3709)	2022-09-14 22:32:28 -07:00
Cargo.toml	Parser: Parse UUIDs; implement comments in AST; implement type annotations and signatures; fix field names (#3653)	2022-09-03 03:15:27 +00:00