[DIAGNOSTIC] README: HTTPS link upgrade — observing required-check behavior#144
Open
laxman-ch wants to merge 1 commit into
Open
[DIAGNOSTIC] README: HTTPS link upgrade — observing required-check behavior#144laxman-ch wants to merge 1 commit into
laxman-ch wants to merge 1 commit into
Conversation
Diagnostic-only one-character HTTPS upgrade. The point of this PR is to observe whether the 4 required full-build-* tests on this repo exhibit the same multi-hour hang behavior we see on PR #140 when the underlying change is unambiguously trivial. If yes, the CI runner / test flakiness is unrelated to that PR and we can route accordingly with the ZK team. Will close this PR once the data point is collected.
adityaagg09
approved these changes
May 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this is
A purpose-built diagnostic PR to isolate whether the multi-hour hang on the required full-build-java-tests and full-build-cppunit-tests jobs is:
branch-3.6's self-hosted runnersChange
README.md: one character —http://zookeeper.apache.org/→https://. Zero touch on Java, build config, tests, or anything else.What we expect to learn
forkcount=1 -Dsurefire.rerunFailingTestsCount=5CI config.Local-suite baseline (for reference, not asserted on this PR)
On commit
c7569c237(PR #140 HEAD), fullmvn -Pfull-build verifyran locally in 28 min withforkcount=4: 3,184 / 3,187 tests pass. Three "failures" all have non-code root causes (JMockit/log4j classpath quirk side effect, forkcount=4 concurrency artifact, fork-specific BackupManager flake).After
Will close this PR after the data point is collected.
🤖 Generated with Claude Code