Store discovered tests in .ty#2636
Merged
Merged
Conversation
added 2 commits
February 13, 2026 18:47
We already used random ports for some tests, which is a good idea since it reduces intermittent issues and makes the testing more robust overall. However, some tests used static ports - this aligns it such that all tests behave the same.
We now store discovered test in .ty files so that it becomes much much cheaper to later retrieve the list of tests. For example, on our own test/stdlib_tests project, before it took upwards of 5 seconds to just list the tests (M4 Pro): acton test list 0.99s user 2.84s system 80% cpu 4.734 total Whereas now it takes a fraction of a second: acton test list 0.06s user 0.10s system 84% cpu 0.182 total 182ms - not bad.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We now store discovered test in .ty files so that it becomes much much
cheaper to later retrieve the list of tests.
For example, on our own test/stdlib_tests project, before it took
upwards of 5 seconds to just list the tests (M4 Pro):
acton test list 0.99s user 2.84s system 80% cpu 4.734 total
Whereas now it takes a fraction of a second:
acton test list 0.06s user 0.10s system 84% cpu 0.182 total
182ms - not bad.
Fixes #2599