Skip to content
Frontend CI

SCRUM 85 #357

Sign in to view logs

SCRUM 85

SCRUM 85 #357

Triggered via pull request September 19, 2024 18:07
@ramesz6ramesz6
synchronize #110
SCRUM-85
Status Failure
Total duration 39s
Artifacts –

frontend-ci.yaml

on: pull_request
build
30s
build
Fit to window
Zoom out
Zoom in

Annotations

4 errors
Unhandled error: frontend/src/pages/PetList.tsx#L18
TypeError: Cannot read properties of undefined (reading 'length') ❯ PetList src/pages/PetList.tsx:18:13 ❯ renderWithHooks node_modules/react-dom/cjs/react-dom.development.js:15486:18 ❯ updateFunctionComponent node_modules/react-dom/cjs/react-dom.development.js:19617:20 ❯ beginWork node_modules/react-dom/cjs/react-dom.development.js:21640:16 ❯ beginWork$1 node_modules/react-dom/cjs/react-dom.development.js:27465:14 ❯ performUnitOfWork node_modules/react-dom/cjs/react-dom.development.js:26599:12 ❯ workLoopSync node_modules/react-dom/cjs/react-dom.development.js:26505:5 ❯ renderRootSync node_modules/react-dom/cjs/react-dom.development.js:26473:7 ❯ recoverFromConcurrentError node_modules/react-dom/cjs/react-dom.development.js:25889:20 ❯ performConcurrentWorkOnRoot node_modules/react-dom/cjs/react-dom.development.js:25789:22 This error originated in "src/pages/PetList.test.tsx" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "displays pets in a table when data is available". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.
Unhandled error: frontend/src/pages/PetList.tsx#L18
TypeError: Cannot read properties of undefined (reading 'length') ❯ PetList src/pages/PetList.tsx:18:13 ❯ renderWithHooks node_modules/react-dom/cjs/react-dom.development.js:15486:18 ❯ updateFunctionComponent node_modules/react-dom/cjs/react-dom.development.js:19617:20 ❯ beginWork node_modules/react-dom/cjs/react-dom.development.js:21640:16 ❯ beginWork$1 node_modules/react-dom/cjs/react-dom.development.js:27465:14 ❯ performUnitOfWork node_modules/react-dom/cjs/react-dom.development.js:26599:12 ❯ workLoopSync node_modules/react-dom/cjs/react-dom.development.js:26505:5 ❯ renderRootSync node_modules/react-dom/cjs/react-dom.development.js:26473:7 ❯ recoverFromConcurrentError node_modules/react-dom/cjs/react-dom.development.js:25889:20 ❯ performConcurrentWorkOnRoot node_modules/react-dom/cjs/react-dom.development.js:25789:22 This error originated in "src/pages/PetList.test.tsx" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "displays a message when no pets are registered". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.
src/pages/PetList.test.tsx > PetList Component > displays pets in a table when data is available: frontend/src/pages/PetList.test.tsx#L36
TestingLibraryElementError: Unable to find an element with the text: Buddy. This could be because the text is broken up by multiple elements. In this case, you can provide a function for your text matcher to make your matcher more flexible. Ignored nodes: comments, script, style <body> <div /> </body> Ignored nodes: comments, script, style <html> <head /> <body> <div /> </body> </html> ❯ Proxy.waitFor node_modules/@testing-library/dom/dist/wait-for.js:163:27 ❯ src/pages/PetList.test.tsx:36:11
build
Process completed with exit code 1.