From 53d9dafe2fdfe27b38d67546809e0474a140fe56 Mon Sep 17 00:00:00 2001 From: Alexander Bokovoy Date: Tue, 15 Feb 2022 14:21:16 +0200 Subject: [PATCH] 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 Reviewed-By: Florence Blanc-Renaud --- ipatests/azure/azure-pipelines.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ipatests/azure/azure-pipelines.yml b/ipatests/azure/azure-pipelines.yml index a920f2852..fd525ba73 100644 --- a/ipatests/azure/azure-pipelines.yml +++ b/ipatests/azure/azure-pipelines.yml @@ -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