-
Notifications
You must be signed in to change notification settings - Fork 238
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
Run entire test suite with multiple values for inliner_aggressiveness
#6390
Comments
You mean literally the entire test suite, with a Github Workflow matrix strategy? I suppose it would help to add support for that value to come from an env var. |
I'll look at the test failures, I see there are some tests which might work similarly to how the stdlib is decorated (and they don't use the CLI). |
By "entire test suite" I meant everything in |
I thought I saw some other kinds of test failures, can't find them now 🙈 |
We recently updated the test suite to run the stdlib tests with a range of potential inliner aggressiveness settings. In #6378 I've updated the default aggressiveness to 0 however this has resulted in a number of compilation failures.
We should update the test suite so that we run it with a range of inliner aggressiveness settings to match how we do it in the stdlib.
The text was updated successfully, but these errors were encountered: