You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/12/14 13:49:00 UTC
[jira] [Updated] (HDDS-2735) Let GitHub Actions run acceptance
check in parallel
[ https://issues.apache.org/jira/browse/HDDS-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated HDDS-2735:
---------------------------------
Labels: pull-request-available (was: )
> Let GitHub Actions run acceptance check in parallel
> ---------------------------------------------------
>
> Key: HDDS-2735
> URL: https://issues.apache.org/jira/browse/HDDS-2735
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Components: build
> Reporter: Attila Doroszlai
> Assignee: Attila Doroszlai
> Priority: Minor
> Labels: pull-request-available
>
> Currently GitHub Actions workflows are configured to run all checks in parallel, except acceptance test. The rationale is that acceptance test takes the most time, and there is no reason to run it if a cheaper check catches some problem.
> I propose to let GitHub Actions run acceptance test in parallel to address the following concerns:
> # Although acceptance test is the slowest (~60 minutes), unit test also takes quite some time (~20-25 minutes). Serializing these two checks increases the time to get feedback on PRs and commits by ~33-40%.
> # For PRs and post-commit builds in forks, running all checks regardless of the result of independent checks allows authors to reduce the number of rounds they need to address any problems.
> # For post-commit builds in Apache master, we expect all checks to pass. However, checks sometime fail eg. due to transient network errors. Skipping acceptance test due to such a problem in another check provides no benefit.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org