HDDS-4406. Run MiniOzoneChaosCluster via github actions.#1532
HDDS-4406. Run MiniOzoneChaosCluster via github actions.#1532mukul1987 wants to merge 1 commit intoapache:masterfrom
Conversation
elek
left a comment
elek
left a comment
There was a problem hiding this comment.
Thanks @mukul1987 the change. Overall it looks good to me.
One missing point might be the collection of available logs as artifacts.
To make it easier I would suggest following the existing convention and create a hadoop-ozone/dev-support/checks/chaos.sh which executes the chaos test and collects all require results under the "$REPORT_DIR".
It would help us to be independent of github actions and execute chaos test in any other (external or internal) environments.
| java: [ 8, 11 ] | ||
| fail-fast: false | ||
| steps: | ||
| - name: Setup link to SSD |
There was a problem hiding this comment.
Just curious: are you sure that root is not on SSD. I know that this secondary partition has more space, but didn't know that it has different hardware (SSD vs HDD).
There was a problem hiding this comment.
This comes from post-commit.yml, where I added this name based on my understanding of the GitHub-hosted runner specification. It says "14 GB of SSD disk space", which matches /mnt, but not the other mount, which has more total space but less free of it.
3 participants
What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
What is the link to the Apache JIRA
(Please create an issue in ASF JIRA before opening a pull request,
and you need to set the title of the pull request which starts with
the corresponding JIRA issue number. (e.g. HDDS-XXXX. Fix a typo in YYY.)
Please replace this section with the link to the Apache JIRA)
How was this patch tested?
(Please explain how this patch was tested. Ex: unit tests, manual tests)
(If this patch involves UI changes, please attach a screen-shot; otherwise, remove this)