-
Notifications
You must be signed in to change notification settings - Fork 327
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
Enable asserts in the tests #4074
Conversation
…ing the HostObjectDebugWrapper workaround in a hope of getting GraalVM 22.3.1 update soon
…Node, when the context is known to exist
0e6fb07
to
5804b28
Compare
engine/runtime/src/main/java/org/enso/interpreter/runtime/data/Type.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't understand the reason for another assert hack in options in the context. AFAIK, all the option keys should already be present in the context, unless there is something wrong with the initialization. I have attached comments on appropriate places.
engine/runtime/src/main/java/org/enso/interpreter/runtime/EnsoContext.java
Show resolved
Hide resolved
interpreterContext.executionService.getContext.getEnvironment.getOptions | ||
.get(RuntimeServerInfo.JOB_PARALLELISM_KEY) | ||
.intValue() | ||
private val jobParallelism = context.getJobParallelism |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
JOB_PARALLELISM_KEY
is registered in RuntimeServerInstrument
. This option descriptor key should be contained in the context. Unless there is something wrong with the initialization of RuntimeServerInstrument
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly minor nits
...uments/src/test/java/org/enso/interpreter/test/instrument/AvoidIdInstrumentationTagTest.java
Show resolved
Hide resolved
engine/runtime/src/main/java/org/enso/interpreter/node/ExpressionNode.java
Show resolved
Hide resolved
engine/runtime/src/main/java/org/enso/interpreter/node/callable/function/BlockNode.java
Show resolved
Hide resolved
engine/runtime/src/main/java/org/enso/interpreter/runtime/EnsoContext.java
Show resolved
Hide resolved
engine/runtime/src/main/java/org/enso/interpreter/runtime/data/Type.java
Outdated
Show resolved
Hide resolved
engine/runtime/src/main/java/org/enso/interpreter/runtime/data/Type.java
Outdated
Show resolved
Hide resolved
engine/runtime/src/test/java/org/enso/interpreter/test/BigNumberTest.java
Outdated
Show resolved
Hide resolved
engine/runtime/src/test/java/org/enso/interpreter/test/BigNumberTest.java
Show resolved
Hide resolved
engine/runtime/src/test/scala/org/enso/interpreter/test/semantic/SystemProcessTest.scala
Show resolved
Hide resolved
…nso into wip/jtulach/EnableAsserts_183546453
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm very glad that we are moving towards testing assertions on the CI 😁
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't agree with some of the style changes introduced here but at the same time I'm not going to be blocking this PR only because of that, considering that we didn't have those checks working for a while.
Pull Request Description
Enso unit tests were running without
-ea
check enabled and as such various invariant checks in Truffle code were not executed. Let's turn the-ea
flag on and fix all the code misbehaves.Checklist
Please include the following checklist in your PR:
Scala,
Java,
and
Rust
style guides.
./run ide build
and./run ide watch
.