Skip to content

[WIP] Improve detecting ops that will not survive after rematerialisation #11079

[WIP] Improve detecting ops that will not survive after rematerialisation

[WIP] Improve detecting ops that will not survive after rematerialisation #11079

Triggered via pull request February 19, 2026 01:28
Status Failure
Total duration 45m 35s
Artifacts

ci.yml

on: pull_request
runner-preparation  /  prepare
4s
runner-preparation / prepare
pre-commit  /  pre-commit (code formatting)
53s
pre-commit / pre-commit (code formatting)
Matrix: build-macos / Build MacOS
Matrix: integration-tests-amd / integration-tests-amd
Matrix: integration-tests-nvidia / integration-tests-nvidia
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 3 warnings
pre-commit / pre-commit (code formatting)
Process completed with exit code 1.
integration-tests-amd / integration-tests-amd (amd-gfx942)
The job has exceeded the maximum execution time of 45m0s
integration-tests-amd / integration-tests-amd (amd-gfx942)
The operation was canceled.
runner-preparation / prepare
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
runner-preparation / prepare
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
runner-preparation / prepare
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/