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

Fix failing toolchain tests #29192

Merged
merged 6 commits into from
May 20, 2024
Merged

Conversation

octylFractal
Copy link
Member

@octylFractal octylFractal commented May 16, 2024

Fixes https://github.com/gradle/gradle-private/issues/4195, fixes https://github.com/gradle/gradle-private/issues/4198, as well as additional issues with assertions failing when the current JDK matched the spec. These tests are now specifically designed to have a spec that will never match the current JDK.

Reviewing cheatsheet

Before merging the PR, comments starting with

  • ❌ ❓must be fixed
  • 🤔 💅 should be fixed
  • 💭 may be fixed
  • 🎉 celebrate happy things

Stacktraces were being written to info logs even when no real failure
was occurring
Fixes issues with provisioning not triggering
@octylFractal octylFractal added a:chore Minor issue without significant impact in:toolchains Java Toolchains labels May 16, 2024
@octylFractal octylFractal added this to the 8.9 RC1 milestone May 16, 2024
@octylFractal octylFractal self-assigned this May 16, 2024
@octylFractal octylFractal requested review from a team as code owners May 16, 2024 16:16
@octylFractal octylFractal requested review from tresat and ov7a and removed request for a team May 16, 2024 16:16
Co-authored-by: Bo Zhang <bo@gradle.com>
Signed-off-by: Octavia Togami <octavia.togami@gmail.com>
@octylFractal
Copy link
Member Author

@bot-gradle help

@bot-gradle
Copy link
Collaborator

Currently, the following commands are supported:

@bot-gradle test <BuildTrigger1> <BuildTrigger2> ... <BuildTriggerN> [without PTS]

Add without PTS to run the build with full test coverage.

  • A trigger is a special build for this PR on TeamCity, common triggers are:
    • SanityCheck/CompileAll/QuickFeedbackLinux/QuickFeedback/PullRequestFeedback/ReadyForNightly/ReadyForRelease
    • Shortcuts: SC/CA/QFL/QF/PRF/RFN/RFR
    • Specific builds:
      • BD: BuildDistributions/BuildDocs so that you can preview the generated docs/distribution.
      • PT: PerformanceTest, all performance tests for Ready For Nightly stage.
      • APT: AllPerformanceTest, all performance tests, including slow performance tests.
      • AST: AllSmokeTestsPullRequestFeedback
      • AFT: AllFunctionalTestsPullRequestFeedback
      • ASB: AllSpecificBuildsPullRequestFeedback
      • ACC: AllConfigCacheTestsPullRequestFeedback
      • ACT: AllCrossVersionTestsReadyForNightly
      • AFTN: AllFunctionalTestsReadyForNightly
      • ACTR: AllCrossVersionTestsReadyForRelease
      • AFTR: AllFunctionalTestsReadyForRelease

@bot-gradle squash

  • Squash the current pull request into a single commit. The squash message will come from the pull request body, with:
    • All Signed-off-by: lines kept.
    • All authors being Co-Authored-By:

@bot-gradle merge

  • Enqueue this PR into GitHub merge queue for merging.
    • GitHub will create a merge commit from your PR branch HEAD and the target branch
    • A GitHub Merge Queue Check Pass build will be triggered on the merge commit
    • When the build passes, the target branch will be fast-forwarded to this merge commit (i.e. merge the PR)

@bot-gradle squash and merge

  • Squash the current pull request into a single commit as described in squash command above,
    then enqueue this PR into GitHub merge queue as described in merge command above.

@bot-gradle cherrypick to <branch>

  • Cherrypicks the current PR to another branch.
    A new PR will be created and a build will triggered automatically if there is no conflict.

@bot-gradle cancel

  • cancel a running build in GitHub merge queue and remove the PR from the queue

@bot-gradle clean

  • clear the conversation history

@bot-gradle help

  • display this message

To run a command, simply submit a comment. For detailed instructions see here.

@octylFractal
Copy link
Member Author

@bot-gradle test AllCrossVersionTestsReadyForNightly AllSmokeTestsPullRequestFeedback

@bot-gradle
Copy link
Collaborator

I've triggered the following builds for you. Click here to see all build failures.

@octylFractal octylFractal added this pull request to the merge queue May 17, 2024
@bot-gradle
Copy link
Collaborator

The merge queue build has failed. Click here to see all failures.

@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks May 17, 2024
@octylFractal octylFractal added this pull request to the merge queue May 20, 2024
@gitstream-cm gitstream-cm bot removed the a:chore Minor issue without significant impact label May 20, 2024
@octylFractal octylFractal removed this pull request from the merge queue due to a manual request May 20, 2024
@octylFractal octylFractal force-pushed the ot/fix/failing-toolchain-tests branch from c23f492 to 22b3e01 Compare May 20, 2024 16:09
@octylFractal octylFractal added this pull request to the merge queue May 20, 2024
@bot-gradle
Copy link
Collaborator

The merge queue build has failed. Click here to see all failures.

Merged via the queue into master with commit e8b99aa May 20, 2024
22 checks passed
@octylFractal octylFractal deleted the ot/fix/failing-toolchain-tests branch May 20, 2024 17:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in:toolchains Java Toolchains
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants