You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should include some binding tests in the required mmtk-core. The tests are expected to finish in roughly half an hour or so (similar to our current mmtk-core 'pre code review' tests). If we include binding tests, the binding tests should cover some features in MMTk core that is only used by that binding, such as conservative stack scanning in Ruby, discontiguous VM space and transitively pinning in Julia.
We may need to allow a way to specify which binding branches to run in the PR description (currently we can only specify binding branches in PR comments). Otherwise the tests will always fail if a PR has API changes.
We should consider renaming our current tests to minimal tests, and extended tests. The name 'binding tests' is confusing, as it sounds like testing the bindings not mmtk-core.
The text was updated successfully, but these errors were encountered:
This PR tries to consolidate the new dacapo chopin tests and the old
dacapo 2006 tests to make them consistent. It also exposes tests to
mmtk-core using Github workflows rather than shell scripts (WIP,
mmtk/mmtk-core#935). It fixes the heap sizes
for 2006 tests (mmtk/mmtk-core#424).
Changes in the PR:
* Separate building from testing when we run dacapo 2006 tests
mmtk-openjdk CI.
* Using moderate heap sizes (proportional to the min heap size) to run
dacapo 2006 tests.
* The old `ci-test.sh` still works (binding tests in the mmtk-core repo
is still functioning).
WIP:
* `test-core-extended.yml` and `test-core-minimal.yml`
(mmtk/mmtk-core#935) needs more work. However,
I cannot test them at the moment. Workflow dispatch only works if the
workflows exist in the default branch. I need to get them merged first,
then start modifying and testing them.
We should include some binding tests in the required mmtk-core. The tests are expected to finish in roughly half an hour or so (similar to our current mmtk-core 'pre code review' tests). If we include binding tests, the binding tests should cover some features in MMTk core that is only used by that binding, such as conservative stack scanning in Ruby, discontiguous VM space and transitively pinning in Julia.
We may need to allow a way to specify which binding branches to run in the PR description (currently we can only specify binding branches in PR comments). Otherwise the tests will always fail if a PR has API changes.
We should consider renaming our current tests to minimal tests, and extended tests. The name 'binding tests' is confusing, as it sounds like testing the bindings not mmtk-core.
The text was updated successfully, but these errors were encountered: