You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-commits@hadoop.apache.org by sl...@apache.org on 2026/10/06 03:05:46 UTC
(hadoop) branch trunk updated: HADOOP-19994. Start PhantomJS with OPENSSL_CONF=/dev/null for catalog webapp Jasmine tests (#8757) Contributed by Jose Luis López
This is an automated email from the ASF dual-hosted git repository.
slfan1989 pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/hadoop.git
The following commit(s) were added to refs/heads/trunk by this push:
new c9c53f2db5d HADOOP-19994. Start PhantomJS with OPENSSL_CONF=/dev/null for catalog webapp Jasmine tests (#8757) Contributed by Jose Luis López
c9c53f2db5d is described below
commit c9c53f2db5d054bd75f11f7673c219bd8305ce8a
Author: Jose Luis López López <jo...@gmail.com>
AuthorDate: Tue Oct 6 05:05:38 2026 +0200
HADOOP-19994. Start PhantomJS with OPENSSL_CONF=/dev/null for catalog webapp Jasmine tests (#8757) Contributed by Jose Luis López
HADOOP-19994. Start PhantomJS with OPENSSL_CONF=/dev/null for Jasmine tests.
PhantomJS 2.1.1 bundles OpenSSL 1.x, which cannot read the OpenSSL 3 configuration used by the Ubuntu Noble precommit image.
It exits before opening its WebDriver port, causing the catalog-webapp Jasmine tests to fail with UnreachableBrowserException.
Add a Unix-only profile that launches PhantomJS through /bin/sh with OPENSSL_CONF=/dev/null,
using the phantomjs.binary.path and phantomjs.cli.args capabilities.
The workaround applies only to the PhantomJS process and allows the existing Jasmine specs to run.
Windows continues to launch PhantomJS directly.
Co-authored-by: Claude Opus 5.5 <no...@anthropic.com>
Co-authored-by: Shilun Fan <sl...@apache.org>
Signed-off-by: Shilun Fan <sl...@apache.org>
---
.../pom.xml | 37 ++++++++++++++++++++++
1 file changed, 37 insertions(+)
diff --git a/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-catalog/hadoop-yarn-applications-catalog-webapp/pom.xml b/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-catalog/hadoop-yarn-applications-catalog-webapp/pom.xml
index 724a91431c1..e96f108bcd7 100644
--- a/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-catalog/hadoop-yarn-applications-catalog-webapp/pom.xml
+++ b/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-catalog/hadoop-yarn-applications-catalog-webapp/pom.xml
@@ -591,6 +591,43 @@
<javascript.test>${test}</javascript.test>
</properties>
</profile>
+ <profile>
+ <!-- PhantomJS 2.1.1 bundles OpenSSL 1.x, which aborts with "Auto
+ configuration failed" (libproviders.so) when it reads an
+ OpenSSL 3 openssl.cnf. Start it through /bin/sh with
+ OPENSSL_CONF=/dev/null, scoped to the PhantomJS process only.
+ Same workaround as RANGER-4791; see ariya/phantomjs#15449. -->
+ <id>phantomjs-openssl-conf</id>
+ <activation>
+ <os>
+ <family>unix</family>
+ </os>
+ </activation>
+ <build>
+ <plugins>
+ <plugin>
+ <groupId>com.github.searls</groupId>
+ <artifactId>jasmine-maven-plugin</artifactId>
+ <configuration>
+ <webDriverCapabilities combine.self="override">
+ <capability>
+ <name>phantomjs.binary.path</name>
+ <value>/bin/sh</value>
+ </capability>
+ <capability>
+ <name>phantomjs.cli.args</name>
+ <list>
+ <arg>-c</arg>
+ <arg>OPENSSL_CONF=/dev/null exec "$0" "$@"</arg>
+ <arg>${phantomjs.binary}</arg>
+ </list>
+ </capability>
+ </webDriverCapabilities>
+ </configuration>
+ </plugin>
+ </plugins>
+ </build>
+ </profile>
<profile>
<id>rest-docs</id>
<build>
---------------------------------------------------------------------
To unsubscribe, e-mail: common-commits-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-commits-help@hadoop.apache.org