Skip to content

Test: compare Gradle download versions (do not merge) - #4546

Closed
andimarek wants to merge 4 commits into
masterfrom
codex/master-ci-control-20261109
Closed

andimarek wants to merge 4 commits into
masterfrom
codex/master-ci-control-20261109

Conversation

@andimarek

@andimarek andimarek commented Nov 9, 2026 •

Copy link
Copy Markdown
Member

Temporary diagnostic PR to compare Gradle distribution download failures seen in #4460. Please do not merge.

Based directly on origin/master at 5b1a5f4f6cf3fd4eb758244d9c6b13a845aec851. The initial documentation-only control reproduced HTTP 504 while downloading Gradle 9.6.1, before compilation or tests: https://github.com/graphql-java/graphql-java/actions/runs/42568177245

The current experiment uses Gradle 9.9.0, still the latest stable release on November 10. This time the Wrapper was also regenerated with Gradle 9.9.0: its JAR and Windows launcher were updated, and the properties explicitly record the default retry settings. The regenerated Wrapper JAR matches Gradle's published SHA-256. A complete download and startup through this Wrapper succeeded from an empty local cache. The original one-word grammar correction in CONTRIBUTING.md is retained.

Results:

Gradle version Fresh local Wrapper download CI
9.6.1 (original master control) HTTP 504 in earlier probes Failed downloading Gradle with HTTP 504
9.9.0 (distribution-only change, November 9) Downloaded completely and started successfully Failed: check job received HTTP 504; Javadoc passed
9.5.1 (older release, November 9) Read timeout during download Failed: Java 21 and Javadoc jobs received HTTP 504 downloading Gradle
9.9.0 with regenerated Wrapper (current branch, November 10) Downloaded completely and started successfully All checks passed, including Java 17/21/25 tests and coverage

The November 9 distribution-version changes did not produce a green build. The failures occurred while fetching Gradle, before the failing jobs executed build tasks. Other matrix jobs were cancelled by fail-fast; a successful coverage gate without a report does not indicate tests ran.

On November 10, rerunning #4460 unchanged with Gradle 9.6.1 also passed every CI check. The download failure therefore appears to have recovered independently of this upgrade; these results do not establish that Gradle 9.9.0 fixed the HTTP 504 problem.

@github-actions

github-actions Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

Test Report

Test Results

Java Version Total Passed Failed Errors Skipped
Java 17 6285 (+23 🟢) 6229 (+23 🟢) 0 (±0) 0 (±0) 56 (±0)
Java 21 6285 (+23 🟢) 6229 (+23 🟢) 0 (±0) 0 (±0) 56 (±0)
Java 25 6285 (+23 🟢) 6229 (+23 🟢) 0 (±0) 0 (±0) 56 (±0)
jcstress 32 (±0) 32 (±0) 0 (±0) 0 (±0) 0 (±0)
Total 18887 (+69 🟢) 18719 (+69 🟢) 0 (±0) 0 (±0) 168 (±0)

Code Coverage (Java 25)

Metric Covered Missed Coverage vs Master
Lines 30448 3077 90.8% ±0.0%
Branches 9010 1504 85.7% +0.1% 🟢
Methods 8118 1186 87.3% ±0.0%

Changed Class Coverage (7 classes)

Class Line Branch Method
g.e.FieldCollector +0.2% 🟢 +0.5% 🟢 ±0.0%
g.u.SelectionSetTraversalFrame +100.0% 🟢 +100.0% 🟢 +100.0% 🟢
g.v.LanguageTraversal removed removed removed
g.v.OperationValidationFrame +97.3% 🟢 +90.0% 🟢 +100.0% 🟢
g.v.OperationValidator +0.2% 🟢 +0.1% 🟢 ±0.0%
g.v.OperationValidator
$1
removed removed removed
g.v.Validator +4.3% 🟢 ±0.0% +11.1% 🟢

Full HTML report: build artifact jacoco-html-report

Updated: 2026-11-09 22:29:58 UTC

@andimarek andimarek changed the title Test: verify CI from current master (do not merge) Test: compare Gradle download versions (do not merge) Nov 9, 2026
@andimarek andimarek closed this Nov 11, 2026
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.

1 participant