Skip to content

Canonicalization should handle transactions that spend from two conflicting transactions #5197

Canonicalization should handle transactions that spend from two conflicting transactions

Canonicalization should handle transactions that spend from two conflicting transactions #5197

Triggered via pull request April 17, 2025 03:55
Status Success
Total duration 4m 45s
Artifacts 1

code_coverage.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Code Coverage
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/
Code Coverage
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/
Code Coverage
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/
Code Coverage
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/

Artifacts

Produced during runtime
Name Size Digest
coverage-report Expired
405 KB
sha256:b10b13826b98de86033da7f685d91758364d0d073725a3c9d89949996a1da10d