Azure CI: don't force non-existing OpenSSL configuration anymore

Newer grunt will pull a PhantomJS that is compatible with newer OpenSSL
so the workaround is not needed anymore.

Additionally, OpenSSL 3.0 is more strict and does not tolerate
non-existing default configuration file.

Signed-off-by: Alexander Bokovoy <abokovoy@redhat.com>
Reviewed-By: Florence Blanc-Renaud <frenaud@redhat.com>
This commit is contained in:
Alexander Bokovoy committed 2022-05-05 17:44:04 +03:00
1 parent 137e62cc2f
commit c2434c4e52
1 file changed
+1 -1
+1 -1
View File
@@ -130,7 +130,7 @@ jobs:
echo "Running WebUI unit tests"
# PhantomJS is not compatible with OpenSSL 1.1.1
# https://github.com/wch/webshot/pull/93
export OPENSSL_CONF=whatever
# export OPENSSL_CONF=whatever
cd $(builddir)/install/ui/js/libs && make
cd $(builddir)/install/ui && npm install
cd $(builddir)/install/ui && node_modules/grunt/bin/grunt --verbose test