Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Actions CI adjustments #3217

Merged
merged 2 commits into from
Jul 13, 2023

Conversation

guilherme-gm
Copy link
Member

@guilherme-gm guilherme-gm commented Jul 9, 2023

Pull Request Prelude

Changes Proposed

  1. Change healthcheck code for actions using MariaDB container.

the current approach of using mysqladmin ping is failing all the time, using the healtcheck script contained in the container image should be enough, since it ensures the instance is reachable

mysql containers still use mysqladmin ping (since healthcheck.sh is not available for them)

from my tests, the issue about failing due to unhealthy MariaDB is fixed. There is still the rare occurrence of one container failing in the overall step, but restarting the specific one works.

  1. Add a 1 hour timeout to all jobs that runs hercules

After fixing MariaDB checks, I noticed that tests that starts/stops Hercules sometimes gets frozen and stays running until it reaches GitHub's default timeout (6 hours). Those jobs usually finish in 10 minutes, with a few exceptions that takes about 30 minutes.

I set their timeout to 1 hour, in case any of the tests end up locked they will fail in 1 hour instead of 6, saving a good amount of runner minutes.

Sample of it failling : https://github.com/guilherme-gm/Hercules/actions/runs/5502605147/jobs/10027096701

Issues addressed:
None

the current approach of using mysqladmin ping was failing all the time,
using the healtcheck script contained in the container image should be
enough, since it ensures the instance is reachable

mysql containers still use mysqladmin ping (since healthcheck.sh is not
available for them)
sometimes the test execution freezes but doesn't fail.
Those tests usually take 30 minutes in the worst case, so using
a timeout of 1 hour will prevent jobs from staying running for
6 hours until the default timeout stops them.
@guilherme-gm guilherme-gm changed the title fix mariadb healthcheck in actions Actions CI adjustments Jul 10, 2023
@MishimaHaruna MishimaHaruna added this to the Release v2023.07.12 milestone Jul 12, 2023
@MishimaHaruna MishimaHaruna merged commit 96a9757 into HerculesWS:master Jul 13, 2023
222 of 254 checks passed
@guilherme-gm guilherme-gm deleted the mariadb-healthcheck branch July 13, 2023 19:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants