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
CI tests currently run for about one hour, which is way too long.
Some ideas how to reduce testing time:
Add "advanced-tests" that are only run when a comment is placed in the PR. See this DoWhy wfl. For example, we could exclude the plotting / API tests and all tests for summarization from the base CI this way.
Add a workflow with a "nightly build" that runs all CI tests, including the advanced tests. See DoWhy's nightly build.
Potentially, re-evaluate if all tests in test_vs_fixest.py are really needed.
Potentially, the installed environments could be cached?
If only the docs are updated, only rebuild the docs, if only the readme is updated, no tests, etc. EconML has some interesting rules in this regard (link)
The text was updated successfully, but these errors were encountered:
s3alfisc
added
the
infrastructure
Everything Related to Package Infrastructure: Github Actions, pre-commit hooks, poetry, linting, etc
label
Sep 15, 2024
CI tests currently run for about one hour, which is way too long.
Some ideas how to reduce testing time:
The text was updated successfully, but these errors were encountered: