Node.js CI with SAM

make more robust to bad input #870

Sign in to view logs

Triggered via push January 17, 2024 21:38

svonworl

feature/seab-5860/send-ecs-stopped-tasks-to-slack

Status Failure

Total duration 6m 2s

Artifacts –

maven.yml

on: push

linterWithESLint

Annotations

7 errors and 2 warnings

linterWithESLint: cloud-watch-to-slack-testing/deployment/index.js#L262

Delete `⏎······`

linterWithESLint: cloud-watch-to-slack-testing/deployment/index.js#L264

Delete `··`

linterWithESLint: cloud-watch-to-slack-testing/deployment/index.js#L265

Delete `··`

linterWithESLint: cloud-watch-to-slack-testing/deployment/index.js#L266

Delete `··`

linterWithESLint: cloud-watch-to-slack-testing/deployment/index.js#L267

Delete `··`

linterWithESLint: cloud-watch-to-slack-testing/deployment/index.js#L268

Replace `··}⏎····` with `}`

linterWithESLint

Process completed with exit code 1.

linterWithESLint

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

testWithSAMCLI

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/