Wasm perf runs are completely broken due to recent changes

[radical]

This has been broken since May 8, like https://dev.azure.com/dnceng/internal/_build/results?buildId=2176141&view=results .

+ python3 -m pip install --user -U pip
/usr/lib/python3/dist-packages/secretstorage/dhcrypto.py:15: CryptographyDeprecationWarning: Python 3.6 is no longer supported by the Python core team. Therefore, support for it is deprecated in cryptography. The next release of cryptography will remove support for Python 3.6.
  from cryptography.utils import int_from_bytes
Requirement already satisfied: pip in /home/helixbot/.local/lib/python3.6/site-packages (21.3.1)
/home/helixbot/work/910D07D6/p/scripts/266ab3989f774d4394cd56c66eb23ada/execute.sh: 6: /home/helixbot/work/910D07D6/p/scripts/266ab3989f774d4394cd56c66eb23ada/execute.sh: cannot open 2: No such file
+ pip3 install urllib3

This seems to be broken since #85915 .
cc @LoopedBard3 @kotlarmilos @lewing

Known Issue Error Message

Fill the error message using known issues guidance.

{
  "ErrorMessage": "",
  "BuildRetry": false
}

Report

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
0	0	0

[ghost]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

---

This has been broken since May 8, like https://dev.azure.com/dnceng/internal/_build/results?buildId=2176141&view=results .

+ python3 -m pip install --user -U pip
/usr/lib/python3/dist-packages/secretstorage/dhcrypto.py:15: CryptographyDeprecationWarning: Python 3.6 is no longer supported by the Python core team. Therefore, support for it is deprecated in cryptography. The next release of cryptography will remove support for Python 3.6.
  from cryptography.utils import int_from_bytes
Requirement already satisfied: pip in /home/helixbot/.local/lib/python3.6/site-packages (21.3.1)
/home/helixbot/work/910D07D6/p/scripts/266ab3989f774d4394cd56c66eb23ada/execute.sh: 6: /home/helixbot/work/910D07D6/p/scripts/266ab3989f774d4394cd56c66eb23ada/execute.sh: cannot open 2: No such file
+ pip3 install urllib3

This seems to be broken since #85915 .
cc @LoopedBard3 @kotlarmilos @lewing

Author:	radical
Assignees:	-
Labels:	blocking-clean-ci, area-Infrastructure, perf-pipeline
Milestone:	-

[LoopedBard3]

Thank you for making this issue to track this, I just merged something to hopefully fix this: b6f6dd0. I will watch to make sure that this fix also fixes the wasm runs, but it will take a little bit to get to that point in the current run.

[LoopedBard3]

That latest update b92c1d2 seems to have fixed the prereq install issues. Waiting for the run to finish to see if there are any downstream issues.

[kotlarmilos]

@LoopedBard3 iOS perf measurements are still broken. Here is one of recent test runs - https://helixri107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-d59c35a3d23442aea5/SOD%20-%20iOS%20HelloWorld%20.app%20Size/1/console.fc85fc43.log?sv=2021-08-06&se=2023-08-08T06%3A47%3A56Z&sr=c&sp=rl&sig=7bOj249carhodQa0xoi5YALZ9%2BCYkt3LAdJDb3ZJvcI%3D.

ImportError: urllib3 v2.0 only supports OpenSSL 1.1.1+, currently the 'ssl' module is compiled with LibreSSL 2.8.3. See: /~https://github.com/urllib3/urllib3/issues/2168

[LoopedBard3]

Added tracking specific for the iOS scenarios to this issue: dotnet/performance#3010. This should allow us to close this issue if there are no more broken WASM runs that I am missing, the main ones appear to be fixed.

[kotlarmilos]

@radical I suggest we close this issue as the issue has been fixed.