feat(models): adding update mechanism #1506
Annotations
10 errors
linter, formatters and unit tests / ubuntu-22.04:
packages/frontend/src/pages/Models.spec.ts#L158
Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
|
linter, formatters and unit tests / ubuntu-22.04:
packages/frontend/src/pages/Models.spec.ts#L251
Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
|
linter, formatters and unit tests / ubuntu-22.04:
packages/frontend/src/pages/Models.spec.ts#L291
Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
|
linter, formatters and unit tests / ubuntu-22.04
Process completed with exit code 2.
|
Unhandled error:
node_modules/@testing-library/svelte/node_modules/@testing-library/dom/dist/@testing-library/dom.esm.js#L1126
TestingLibraryElementError: Unable to find an element with the text: dummy-name. 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
<div
class="whitespace-nowrap justify-self-start"
role="cell"
/>
Ignored nodes: comments, script, style
<div
class="whitespace-nowrap justify-self-start"
role="cell"
/>
❯ waitForWrapper ../../node_modules/@testing-library/svelte/node_modules/@testing-library/dom/dist/@testing-library/dom.esm.js:1126:27
❯ ../../node_modules/@testing-library/svelte/node_modules/@testing-library/dom/dist/@testing-library/dom.esm.js:1206:12
❯ src/pages/Models.spec.ts:154:33
This error originated in "src/pages/Models.spec.ts" 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 "Import button should redirect to import page". 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.
|
linter, formatters and unit tests / macos-12
Process completed with exit code 1.
|
linter, formatters and unit tests / windows-2022:
packages/frontend/src/pages/Models.spec.ts#L158
Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
|
linter, formatters and unit tests / windows-2022:
packages/frontend/src/pages/Models.spec.ts#L251
Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
|
linter, formatters and unit tests / windows-2022:
packages/frontend/src/pages/Models.spec.ts#L291
Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
|
linter, formatters and unit tests / windows-2022
Process completed with exit code 1.
|