Skip to content
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

Tests: Run expensive kernel tests in another stage #89

Open
LinqLover opened this issue Jul 23, 2022 · 0 comments
Open

Tests: Run expensive kernel tests in another stage #89

LinqLover opened this issue Jul 23, 2022 · 0 comments
Labels
development Concerns internal quality (tests, performance, automation, ...)

Comments

@LinqLover
Copy link
Collaborator

A large portion of the test run in under 15 seconds, but there are a few larger tests:

  • kernel tests (> 200 seconds)
  • (maybe help tests - download figure)
  • (maybe UI tests) (~ 20 seconds locally)

By moving the large tests into a separate CI stage, we could receive earlier feedback on failures.

Things to consider:

  • How large would the overhead of running smalltalkCI twice be? How can we reuse the image?
  • Apply the same solution to SimulationStudio as well
  • Are there further outliers in the kernel tests that could be avoided/eliminated?
@LinqLover LinqLover added the development Concerns internal quality (tests, performance, automation, ...) label Jul 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
development Concerns internal quality (tests, performance, automation, ...)
Projects
None yet
Development

No branches or pull requests

1 participant