Skip to content

equivalence feedback gives in terms of user entered atoms, not expect… #51

equivalence feedback gives in terms of user entered atoms, not expect…

equivalence feedback gives in terms of user entered atoms, not expect… #51

Triggered via push March 12, 2026 06:02
Status Success
Total duration 1m 33s
Artifacts 4

deploy.yml

on: push
Matrix: Test
Deploy to Lambda Feedback  /  Setup
3s
Deploy to Lambda Feedback / Setup
Build Docker Image  /  Build and Push Docker Image
1m 13s
Build Docker Image / Build and Push Docker Image
Matrix: Deploy to Lambda Feedback / build-aws
Matrix: Deploy to Lambda Feedback / build-gcp
Waiting for pending jobs
Deploy to Lambda Feedback  /  ...  /  Deploy (staging)
6s
Deploy to Lambda Feedback / deploy-staging-aws / Deploy (staging)
Deploy to Lambda Feedback  /  ...  /  Deploy (production)
7s
Deploy to Lambda Feedback / deploy-production-aws / Deploy (production)
Deploy to Lambda Feedback  /  ...  /  deploy
Deploy to Lambda Feedback / deploy-gcp-production / deploy
Deploy to Lambda Feedback  /  ...  /  deploy
Deploy to Lambda Feedback / deploy-gcp-staging / deploy
Fit to window
Zoom out
Zoom in

Annotations

7 warnings
Test (3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Deploy to Lambda Feedback / Setup
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. 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/
Deploy to Lambda Feedback / build-aws (staging) / Build (staging)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/amazon-ecr-login@v2, aws-actions/configure-aws-credentials@v4, docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Deploy to Lambda Feedback / build-aws (production) / Build (production)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/amazon-ecr-login@v2, aws-actions/configure-aws-credentials@v4, docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Build Docker Image / Build and Push Docker Image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Deploy to Lambda Feedback / deploy-staging-aws / Deploy (staging)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/configure-aws-credentials@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Deploy to Lambda Feedback / deploy-production-aws / Deploy (production)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/configure-aws-credentials@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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
lambda-feedback~Propositional-logic-eval~8R0MFH.dockerbuild
39.5 KB
sha256:013d8abcd0443c83faa5835db19ad65bc38f045685902dcc653d546558b02001
lambda-feedback~Propositional-logic-eval~93AV68.dockerbuild
45 KB
sha256:37e16d86c6d887b143f333d634e4225de9414b44d074d5fe41e7fd1afcd8b576
lambda-feedback~Propositional-logic-eval~JTVLOX.dockerbuild
39.1 KB
sha256:d48f5296918c4bfb06f6e33e0ee8d18b6cc24fe703b4405789f042010ba7e228
test-results
686 Bytes
sha256:caa2e420128533d7e0877331e9fe5002ff7faef2c3269f5d9050fadcd5af7cc2