Run link checker GitHub action on schedule.

[adnapibar]

Description

Most PRs do not add/update links, however sites go down often. This change makes sure that we catch any broken links in the repository and fix it, but at the same time we do not block PRs because of some unrelated broken link.

This PR updates the workflow to run everyday at midnight UTC.

Issues Resolved

N/A

Check List

• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Signed-off-by: Rabi Panda adnapibar@gmail.com

[opensearch-ci-bot]

✅   DCO Check Passed f0a8acf

[opensearch-ci-bot]

✅   Gradle Wrapper Validation success f0a8acf

[opensearch-ci-bot]

✅   Gradle Precommit success f0a8acf

[VachaShah]

Since we are not running link checker on PR and push, how are we planning to track if there are any broken links? Would it be easier if we added some report at the end of the run which can easily show if there are any broken links? May be something like: https://github.com/lycheeverse/lychee-action#usage

[dblock]

Since we are not running link checker on PR and push, how are we planning to track if there are any broken links? Would it be easier if we added some report at the end of the run which can easily show if there are any broken links? May be something like: https://github.com/lycheeverse/lychee-action#usage

When builds fail maintainers get GitHub notifications, IMHO this is sufficient.

[adnapibar]

start gradle check

[opensearch-ci-bot]

❌   Gradle Check failure f0a8acf
Log 502

Reports 502

[adnapibar]

start gradle check

[opensearch-ci-bot]

❌   Gradle Check failure f0a8acf
Log 505

Reports 505

[adnapibar]

Failing test not reproducible

REPRODUCE WITH: ./gradlew ':server:internalClusterTest' --tests "org.opensearch.cluster.ClusterHealthIT.testHealthOnMasterFailover" -Dtests.seed=47EB5C58644C9840 -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1" -Dtests.locale=nl-NL -Dtests.timezone=America/St_Thomas -Druntime.java=15
  2> java.util.concurrent.ExecutionException: MasterNotDiscoveredException[NodeDisconnectedException[[node_s1][127.0.0.1:40191][cluster:monitor/health] disconnected]]; nested: NodeDisconnectedException[[node_s1][127.0.0.1:40191][cluster:monitor/health] disconnected];
        at __randomizedtesting.SeedInfo.seed([47EB5C58644C9840:D904737567A684A6]:0)
        at org.opensearch.common.util.concurrent.BaseFuture$Sync.getValue(BaseFuture.java:286)
        at org.opensearch.common.util.concurrent.BaseFuture$Sync.get(BaseFuture.java:273)
        at org.opensearch.common.util.concurrent.BaseFuture.get(BaseFuture.java:100)
        at org.opensearch.cluster.ClusterHealthIT.testHealthOnMasterFailover(ClusterHealthIT.java:357)

[adnapibar]

start gradle check

[opensearch-ci-bot]

✅   Gradle Check success f0a8acf
Log 508

Reports 508

[saratvemulapalli]

Failing test not reproducible

REPRODUCE WITH: ./gradlew ':server:internalClusterTest' --tests "org.opensearch.cluster.ClusterHealthIT.testHealthOnMasterFailover" -Dtests.seed=47EB5C58644C9840 -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1" -Dtests.locale=nl-NL -Dtests.timezone=America/St_Thomas -Druntime.java=15
  2> java.util.concurrent.ExecutionException: MasterNotDiscoveredException[NodeDisconnectedException[[node_s1][127.0.0.1:40191][cluster:monitor/health] disconnected]]; nested: NodeDisconnectedException[[node_s1][127.0.0.1:40191][cluster:monitor/health] disconnected];
        at __randomizedtesting.SeedInfo.seed([47EB5C58644C9840:D904737567A684A6]:0)
        at org.opensearch.common.util.concurrent.BaseFuture$Sync.getValue(BaseFuture.java:286)
        at org.opensearch.common.util.concurrent.BaseFuture$Sync.get(BaseFuture.java:273)
        at org.opensearch.common.util.concurrent.BaseFuture.get(BaseFuture.java:100)
        at org.opensearch.cluster.ClusterHealthIT.testHealthOnMasterFailover(ClusterHealthIT.java:357)

Could we open an issue to track this, seems like this this is flaky.
This PR: #1230 (comment) is also seeing a similar problem.

[adnapibar]

Could we open an issue to track this, seems like this this is flaky.
This PR: #1230 (comment) is also seeing a similar problem.

The failure is not reproducible with the same random seed, so don't think the test is flaky, maybe some issue with the environment. We are working on periodically running randomized testing on the CI and capturing the failures in one consolidated place (maybe a meta issue). IMO, creating a separate issue for all such failures at this point is going to create a lot of noise.

[saratvemulapalli]

Could we open an issue to track this, seems like this this is flaky.
This PR: #1230 (comment) is also seeing a similar problem.

The failure is not reproducible with the same random seed, so don't think the test is flaky, maybe some issue with the environment. We are working on periodically running randomized testing on the CI and capturing the failures in one consolidated place (maybe a meta issue). IMO, creating a separate issue for all such failures at this point is going to create a lot of noise.

Absolutely that makes sense to me.