Repository navigation
Skip the browser tests where no browser driver can be obtained - #19
Merged
Merged
Conversation
The JavaScript builder tests drive a headless browser that Selenium Manager provides, and it has no build for Linux on ARM. The separate Pipeline API repository never ran on an ARM runner, but this repository runs every tree's tests on every configuration, so on ARM the class is skipped with the reason rather than failed. Everywhere a driver exists the tests run as before.
ben51degrees
marked this pull request as ready for review
November 2, 2026 20:12
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
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.
The Pull Requests workflow failed on Ubuntu_ARM_Java_17 in JavaScriptBuilderTests: Selenium Manager has no Linux ARM build, so it cannot obtain chromedriver. The separate Pipeline API repository never ran on an ARM runner, but this repository runs every tree's unit tests on every configuration, and the ARM configuration comes from the engines' matrices because it builds their ARM native library.
Change
When creating the shared driver in the class setup throws because no driver can be obtained, the class is skipped with the reason. Everywhere a driver exists, nothing changes.
What was checked