Skip to content

Conversation

@donoghuc
Copy link
Member

Release notes

[rn:skip]

What does this PR do?

Previously unit tests were run with a subset of gems. This masked issues where conflicts (specifically with loading jar-dependencies) with gem load/activation were causing issues. This updates the tests to install the full gem set for unit tests. The added test time is minimal (less than a minute) and should give us a more consistent gem environment for testing.

See #17873 for more details.

Previously unit tests were run with a subset of gems. This masked issues where
conflicts (specifically with loading jar-dependencies) with gem load/activation
were causing issues. This updates the tests to install the full gem set for unit
tests. The added test time is minimal (less than a minute) and should give us a
more consistent gem environment for testing.
@github-actions
Copy link
Contributor

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

@mergify
Copy link
Contributor

mergify bot commented Oct 21, 2025

This pull request does not have a backport label. Could you fix it @donoghuc? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit.
  • If no backport is necessary, please add the backport-skip label

@donoghuc donoghuc added the backport-active-all Automated backport with mergify to all the active branches label Oct 21, 2025
@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-active-all Automated backport with mergify to all the active branches

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants