failed Pipeline #2289 triggered by Kelve Oliveira's avatar Kelve Oliveira

refactor: corrigindo sintaxe no código

1 job for !164 with 178-usar-o-env-no-frontend-adicionar-url-da-api in 19 seconds (queued for 1 second)
latest detached
Status Job ID Name Coverage
  Test
failed #5950
testar-app

00:00:19

 
Name Stage Failure
failed
testar-app Test
npm error syscall open
npm error path /builds/f-brica-de-software-ii-2024-1/visualizacao-sala/package.json
npm error errno -2
npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '/builds/f-brica-de-software-ii-2024-1/visualizacao-sala/package.json'
npm error enoent This is related to npm not being able to find a file.
npm error enoent
npm error A complete log of this run can be found in: /root/.npm/_logs/2025-02-19T01_36_04_232Z-debug-0.log
Cleaning up project directory and file based variables
ERROR: Job failed: exit code 254

Speed up your pipelines with Needs relationships

Using the needs keyword makes jobs run before their stage is reached. Jobs run as soon as their needs relationships are met, which speeds up your pipelines.

If you add needs to jobs in your pipeline you'll be able to view the needs relationships between jobs in this tab as a Directed Acyclic Graph (DAG).

There are no tests to show.