[
https://issues.apache.org/jira/browse/HDDS-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Viswanadham updated HDDS-2735:
-------------------------------------
Fix Version/s: 0.5.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> 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
> Fix For: 0.5.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
