Skip to content

Fix out-of-bounds memory access in SetKernel for 0-size tensor #15140

Fix out-of-bounds memory access in SetKernel for 0-size tensor

Fix out-of-bounds memory access in SetKernel for 0-size tensor #15140

Triggered via pull request March 28, 2026 03:28
Status Success
Total duration 2h 2m 27s
Artifacts

CI-Windows.yml

on: pull_request
Check file paths
1m 4s
Check file paths
Clone-windows  /  Clone Paddle
1m 59s
Clone-windows / Clone Paddle
Windows-GPU  /  ...  /  Check bypass
5s
Windows-GPU / Check bypass / Check bypass
Windows-Inference  /  ...  /  Check bypass
6s
Windows-Inference / Check bypass / Check bypass
Windows-OPENBLAS  /  ...  /  Check bypass
5s
Windows-OPENBLAS / Check bypass / Check bypass
Windows-GPU  /  Build and test
1h 30m
Windows-GPU / Build and test
Windows-Inference  /  Build and test
1h 59m
Windows-Inference / Build and test
Windows-OPENBLAS  /  Build and test
48m 46s
Windows-OPENBLAS / Build and test
Fit to window
Zoom out
Zoom in

Annotations

1 warning
Check file paths
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 will be forced to run with Node.js 24 by default starting June 2nd, 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/