[CI] Grant pull-requests write to the benchmark PR-comment workflow (… #9900
benchmarks.yml
on: push
Matrix: benchmark
Upload benchmark results
40s
Annotations
5 errors and 4 warnings
|
CPU 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.
|
|
CPU 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
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
|
|
Upload benchmark results
# :warning: **Performance Alert** :warning:
Possible performance regression was detected for benchmark **'CPU Benchmark Results'**.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold `2`.
| Benchmark suite | Current: 26ece893cbedcf467a2819b61475857506a083e0 | Previous: 45aa2e2a371749eaf626913c7fc00f2e6911cea4 | Ratio |
|-|-|-|-|
| `benchmarks/test_replaybuffer_benchmark.py::test_rb_populate[TensorDictPrioritizedReplayBuffer-ListStorage-None-400]` | `51.28870708335402` iter/sec (`stddev: 0.1004169215120585`) | `188.14859666028846` iter/sec (`stddev: 0.0009743167703541905`) | `3.67` |
This comment was automatically generated by [workflow](https://github.com/pytorch/rl/actions?query=workflow%3AContinuous%20Benchmark) using [github-action-benchmark](https://github.com/marketplace/actions/continuous-benchmark).
CC: @vmoens
|
|
CPU Pytest benchmark
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
GPU Pytest benchmark
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Upload benchmark results
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Upload benchmark results
Performance alert! Previous value was 188.14859666028846 and current value is 51.28870708335402. It is 3.668421517323702x worse than previous exceeding a ratio threshold 2
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
CPU-benchmark-results
|
2.83 MB |
sha256:ffce7868af1b41bbe9ff61edd0742b75fcd0f7cacb4611b4a6814964d81e6014
|
|
|
GPU-benchmark-results
|
2.98 MB |
sha256:3723fde15b7cf31f013ec68d2d5ce1ce09310e4fef114abc8ad30df22e4d40c3
|
|