refactor(AtLocation): allow throwing a warning when no progress is being made #288592
grunwegbuild_fork.yml
on: pull_request_target
ci (fork)
/
Build
50m 44s
ci (fork)
/
Lint style
2m 11s
ci (fork)
/
Post-CI job
0s
Annotations
5 errors and 2 warnings
|
ci (fork) / Build
Process completed with exit code 1.
|
|
ci (fork) / Build
❌️ Docstring on `#guard_msgs` does not match generated message:
|
|
ci (fork) / Build
``abel_nf`` made no progress anywhere
|
|
ci (fork) / Build
❌️ Docstring on `#guard_msgs` does not match generated message:
|
|
ci (fork) / Build
``push Not`` made no progress anywhere
|
|
ci (fork) / Lint style
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065. 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/
|
|
ci (fork) / Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: leanprover-community/gh-problem-matcher-wrap@20007cb926a46aa324653a387363b52f07709845. 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
cache-staging
|
330 MB |
sha256:97c1062cfc92ec9c66c914269e3a6acc2dd992188f63e909ac2b440cd2d1bd99
|
|