Selenium::Remote::Driver 1.50 hangs during PerlOnJava tests
Selenium::Remote::Driver-1.50 reaches its test phase under PerlOnJava but produces no TAP output and does not complete. The archived CPAN report ends immediately after launching the target test harness.
System Perl comparison
The distribution and its test dependencies were installed into an isolated temporary Perl library (the global system Perl was not modified). With that library, system Perl passes the complete suite:
Files=35, Tests=385
Result: PASS
The suite completes in about 10 seconds. The tests use mocked Selenium connections; they do not require a live Selenium server or browser for this result.
PerlOnJava reproduction
Using the target build's dependency overlay:
timeout 120 ./jperl -MExtUtils::Command::MM -MTest::Harness \\
-e 'undef *Test::Harness::Switches; test_harness(0, "blib/lib", "blib/arch")' \\
t/*.t
The PerlOnJava run produces no test output and hangs until bounded externally. The original CPAN report shows the same behavior after launching make test.
This is not a missing-dependency, browser-service, or upstream test failure: system Perl passes the same suite, and the target tests are mock-based. It appears to be a PerlOnJava test/runtime hang. The backend affected should be confirmed with separate JVM and interpreter focused runs.
Archived report:
/tmp/cpan_random_logs/20260824-171428-41866/failures/Selenium-Remote-Driver--from--Selenium-Remote-Driver.log
Selenium::Remote::Driver 1.50 hangs during PerlOnJava tests
Selenium::Remote::Driver-1.50reaches its test phase under PerlOnJava but produces no TAP output and does not complete. The archived CPAN report ends immediately after launching the target test harness.System Perl comparison
The distribution and its test dependencies were installed into an isolated temporary Perl library (the global system Perl was not modified). With that library, system Perl passes the complete suite:
The suite completes in about 10 seconds. The tests use mocked Selenium connections; they do not require a live Selenium server or browser for this result.
PerlOnJava reproduction
Using the target build's dependency overlay:
The PerlOnJava run produces no test output and hangs until bounded externally. The original CPAN report shows the same behavior after launching
make test.This is not a missing-dependency, browser-service, or upstream test failure: system Perl passes the same suite, and the target tests are mock-based. It appears to be a PerlOnJava test/runtime hang. The backend affected should be confirmed with separate JVM and interpreter focused runs.
Archived report:
/tmp/cpan_random_logs/20260824-171428-41866/failures/Selenium-Remote-Driver--from--Selenium-Remote-Driver.log