Skip to content
Build

AA-526: Store the frame entry opcode as part of the violation object #1262

Sign in to view logs

AA-526: Store the frame entry opcode as part of the violation object

AA-526: Store the frame entry opcode as part of the violation object #1262

Triggered via pull request February 4, 2025 23:24
@forshtatforshtat
synchronize #244
AA-526-rules-after-delegatecall
Status Success
Total duration 5m 14s
Artifacts –

build.yml

on: pull_request
test
2m 9s
test
lint
5m 4s
lint
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
test
Your workflow is using a version of actions/cache that is scheduled for deprecation, actions/cache@v2. Please update your workflow to use either v3 or v4 of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-12-05-notice-of-upcoming-releases-and-breaking-changes-for-github-actions/#actions-cache-v1-v2-and-actions-toolkit-cache-package-closing-down
lint
Your workflow is using a version of actions/cache that is scheduled for deprecation, actions/cache@v2. Please update your workflow to use either v3 or v4 of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-12-05-notice-of-upcoming-releases-and-breaking-changes-for-github-actions/#actions-cache-v1-v2-and-actions-toolkit-cache-package-closing-down