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
What is the feature you think should be a good addition to Dangerzone?
Dangerzone has a test suite with a large number of documents, that we tend to run before each release. We usually run this locally, but it takes quite a lot of time and space. It would be best to run it in GitHub Actions. The test suite is documented here: https://github.com/freedomofpress/dangerzone/blob/main/docs/developer/TESTING.md
Is your feature request related to a problem? Please describe.
This test suite is useful for detecting regressions in our code, so it's good to run it in regular intervals.
Additional context
Anecdotally, running this test suite locally takes about a day. On the other hand, GitHub's Usage Limits state that jobs can run for a maximum of 6 hours:
Job execution time - Each job in a workflow can run for up to 6 hours of execution time. If a job reaches this limit, the job is terminated and fails to complete.
What is the feature you think should be a good addition to Dangerzone?
Dangerzone has a test suite with a large number of documents, that we tend to run before each release. We usually run this locally, but it takes quite a lot of time and space. It would be best to run it in GitHub Actions. The test suite is documented here: https://github.com/freedomofpress/dangerzone/blob/main/docs/developer/TESTING.md
Is your feature request related to a problem? Please describe.
This test suite is useful for detecting regressions in our code, so it's good to run it in regular intervals.
Additional context
Anecdotally, running this test suite locally takes about a day. On the other hand, GitHub's Usage Limits state that jobs can run for a maximum of 6 hours:
Luckily, GitHub allows us to run 20 concurrent jobs in our free plan. There are people who have taken advantage of this fact to parallelize their
pytest
invocations: https://github.com/jerry-git/pytest-split-gh-actions-demo/blob/master/.github/workflows/test.ymlSee also:
The text was updated successfully, but these errors were encountered: