[Algorithm] Update scripts with compile #5099
Triggered via pull request
September 23, 2024 14:07
Status
Failure
Total duration
35m 15s
Artifacts
–
benchmarks_pr.yml
on: pull_request
CPU Pytest benchmark
24m 17s
GPU Pytest benchmark
31m 47s
Annotations
3 errors and 4 warnings
GPU Pytest benchmark
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
|
GPU Pytest benchmark
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
|
GPU Pytest benchmark
Workflow failed! Cannot read properties of undefined (reading 'ops')
|
CPU Pytest benchmark
The following actions uses node12 which is deprecated and will be forced to run on node16: apbard/pytest-benchmark-commenter@v3. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
CPU Pytest benchmark
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, apbard/pytest-benchmark-commenter@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
GPU Pytest benchmark
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-python@v4, apbard/pytest-benchmark-commenter@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
GPU Pytest benchmark
The following actions uses node12 which is deprecated and will be forced to run on node16: apbard/pytest-benchmark-commenter@v3. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|