chore: Shared/utils conversions Part 2 Part 1 #5851
ajay-sentryci.yml
on: pull_request
Install deps
17s
Build Self Hosted Image
/
Build Self Hosted App
4m 39s
Codecov Startup
/
Codecov Startup
24s
Generate runner indexes Vitest
4s
Run Lint
1m 3s
Run Type Checker
49s
Run Prettier Check
36s
Upload Bundle Stats - Production
1m 47s
Upload Bundle Stats - Staging
1m 53s
Run storybook
1m 55s
Run Fossa
12s
Build Self Hosted Image
/
Push Self Hosted Image
0s
Build Self Hosted Image
/
Push Self Hosted Release Image
0s
Matrix: test-vitest
Build App
0s
Push Self Hosted Image
/
Push Self Hosted Image
Push Self Hosted Image
/
Push Self Hosted Release Image
Annotations
33 errors and 1 warning
|
Unhandled error:
src/ui/Dropdown/Dropdown.tsx#L80
ReferenceError: window is not defined
❯ getCurrentEventPriority node_modules/react-dom/cjs/react-dom.development.js:10993:22
❯ requestUpdateLane node_modules/react-dom/cjs/react-dom.development.js:25495:19
❯ setWasJustClosed node_modules/react-dom/cjs/react-dom.development.js:16648:14
❯ Timeout._onTimeout src/ui/Dropdown/Dropdown.tsx:80:8
❯ listOnTimeout node:internal/timers:581:17
❯ processTimers node:internal/timers:519:7
This error originated in "src/App.test.tsx" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
This error was caught after test environment was torn down. Make sure to cancel any running tasks before test finishes:
- cancel timeouts using clearTimeout and clearInterval
- wait for promises to resolve using the await keyword
|
|
Unhandled error:
src/ui/Dropdown/Dropdown.tsx#L80
ReferenceError: window is not defined
❯ getCurrentEventPriority node_modules/react-dom/cjs/react-dom.development.js:10993:22
❯ requestUpdateLane node_modules/react-dom/cjs/react-dom.development.js:25495:19
❯ setWasJustClosed node_modules/react-dom/cjs/react-dom.development.js:16648:14
❯ Timeout._onTimeout src/ui/Dropdown/Dropdown.tsx:80:8
❯ listOnTimeout node:internal/timers:581:17
❯ processTimers node:internal/timers:519:7
This error originated in "src/App.test.tsx" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
This error was caught after test environment was torn down. Make sure to cancel any running tasks before test finishes:
- cancel timeouts using clearTimeout and clearInterval
- wait for promises to resolve using the await keyword
|
|
src/pages/AccountSettings/AccountSettings.test.jsx > AccountSettings > on root route > is self hosted > user is viewing personal settings > displays profile tab:
src/pages/AccountSettings/AccountSettings.test.jsx#L180
TestingLibraryElementError: Unable to find an element with the text: Profile. 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
<body>
<div />
</body>
❯ waitForWrapper node_modules/@testing-library/dom/dist/wait-for.js:163:27
❯ node_modules/@testing-library/dom/dist/query-helpers.js:86:33
❯ src/pages/AccountSettings/AccountSettings.test.jsx:180:43
|
|
src/pages/AccountSettings/AccountSettings.test.jsx > AccountSettings > on root route > is self hosted > user is not viewing personal settings > redirects the user to the yaml tab:
src/pages/AccountSettings/AccountSettings.test.jsx#L193
TestingLibraryElementError: Unable to find an element with the text: YAML. 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
<body>
<div />
</body>
❯ waitForWrapper node_modules/@testing-library/dom/dist/wait-for.js:163:27
❯ node_modules/@testing-library/dom/dist/query-helpers.js:86:33
❯ src/pages/AccountSettings/AccountSettings.test.jsx:193:40
|
|
src/pages/AccountSettings/AccountSettings.test.jsx > AccountSettings > on root route > is not self hosted > user is an admin > displays the admin tab:
src/pages/AccountSettings/AccountSettings.test.jsx#L208
TestingLibraryElementError: Unable to find an element with the text: Admin. 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
<body>
<div />
</body>
❯ waitForWrapper node_modules/@testing-library/dom/dist/wait-for.js:163:27
❯ node_modules/@testing-library/dom/dist/query-helpers.js:86:33
❯ src/pages/AccountSettings/AccountSettings.test.jsx:208:41
|
|
src/pages/AccountSettings/AccountSettings.test.jsx > AccountSettings > on root route > is not self hosted > user is not an admin > redirects user to yaml tab:
src/pages/AccountSettings/AccountSettings.test.jsx#L221
TestingLibraryElementError: Unable to find an element with the text: YAML. 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
<body>
<div />
</body>
❯ waitForWrapper node_modules/@testing-library/dom/dist/wait-for.js:163:27
❯ node_modules/@testing-library/dom/dist/query-helpers.js:86:33
❯ src/pages/AccountSettings/AccountSettings.test.jsx:221:40
|
|
src/pages/AccountSettings/AccountSettings.test.jsx > AccountSettings > on root route > redirects the user to the yaml tab:
src/pages/AccountSettings/AccountSettings.test.jsx#L234
TestingLibraryElementError: Unable to find an element with the text: YAML. 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
<body>
<div />
</body>
❯ waitForWrapper node_modules/@testing-library/dom/dist/wait-for.js:163:27
❯ node_modules/@testing-library/dom/dist/query-helpers.js:86:33
❯ src/pages/AccountSettings/AccountSettings.test.jsx:234:36
|
|
src/pages/AccountSettings/AccountSettings.test.jsx > AccountSettings > on the yaml route > renders the yaml tab:
src/pages/AccountSettings/AccountSettings.test.jsx#L250
TestingLibraryElementError: Unable to find an element with the text: YAML. 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
<body>
<div />
</body>
❯ waitForWrapper node_modules/@testing-library/dom/dist/wait-for.js:163:27
❯ node_modules/@testing-library/dom/dist/query-helpers.js:86:33
❯ src/pages/AccountSettings/AccountSettings.test.jsx:250:36
|
|
src/pages/AccountSettings/AccountSettings.test.jsx > AccountSettings > on the access route > is self hosted > hide access tab is set to false > renders access tab:
src/pages/AccountSettings/AccountSettings.test.jsx#L268
TestingLibraryElementError: Unable to find an element with the text: Access. 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
<body>
<div />
</body>
❯ waitForWrapper node_modules/@testing-library/dom/dist/wait-for.js:163:27
❯ node_modules/@testing-library/dom/dist/query-helpers.js:86:33
❯ src/pages/AccountSettings/AccountSettings.test.jsx:268:42
|
|
src/pages/AccountSettings/AccountSettings.test.jsx > AccountSettings > on the access route > is self hosted > hide access tab is set to true > renders not found tab:
src/pages/AccountSettings/AccountSettings.test.jsx#L284
TestingLibraryElementError: Unable to find an element with the text: NotFound. 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
<body>
<div />
</body>
❯ waitForWrapper node_modules/@testing-library/dom/dist/wait-for.js:163:27
❯ node_modules/@testing-library/dom/dist/query-helpers.js:86:33
❯ src/pages/AccountSettings/AccountSettings.test.jsx:284:41
|
|
Test Runner #7 - Vitest
The job was canceled because "_0" failed.
|
|
Test Runner #4 - Vitest
The job was canceled because "_0" failed.
|
|
src/pages/RepoPage/CoverageOnboarding/ActivationBanner/ActivationBanner.test.tsx > ActivationBanner > renders activation required banner if user is not on free plan and has seats left:
src/pages/RepoPage/CoverageOnboarding/ActivationBanner/ActivationBanner.test.tsx#L117
TestingLibraryElementError: Unable to find an element with the text: /ActivationRequiredBanner/. 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>
PaidPlanSeatsLimitBanner
</div>
</body>
Ignored nodes: comments, script, style
<body>
<div>
PaidPlanSeatsLimitBanner
</div>
</body>
❯ waitForWrapper node_modules/@testing-library/dom/dist/wait-for.js:163:27
❯ node_modules/@testing-library/dom/dist/query-helpers.js:86:33
❯ src/pages/RepoPage/CoverageOnboarding/ActivationBanner/ActivationBanner.test.tsx:117:51
|
|
Test Runner #4 - Vitest
Process completed with exit code 1.
|
|
Test Runner #4 - Vitest
The operation was canceled.
|
|
Test Runner #1 - Vitest
The job was canceled because "_0" failed.
|
|
Test Runner #1 - Vitest
The operation was canceled.
|
|
src/pages/OwnerPage/HeaderBanners/HeaderBanners.test.jsx > HeaderBanners > displaying ExceededUploadsAlert banner > org has exceeded limit > displays the banner:
src/pages/OwnerPage/HeaderBanners/HeaderBanners.test.jsx#L119
TestingLibraryElementError: Unable to find an element with the text: Upload limit has been reached. 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
<body>
<div />
</body>
❯ waitForWrapper node_modules/@testing-library/dom/dist/wait-for.js:163:27
❯ node_modules/@testing-library/dom/dist/query-helpers.js:86:33
❯ src/pages/OwnerPage/HeaderBanners/HeaderBanners.test.jsx:119:37
|
|
src/pages/OwnerPage/HeaderBanners/HeaderBanners.test.jsx > HeaderBanners > displaying ReachingUploadLimit banner > org has exceeded limit > displays the banner:
src/pages/OwnerPage/HeaderBanners/HeaderBanners.test.jsx#L163
TestingLibraryElementError: Unable to find an element with the text: Upload limit almost reached. 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
<body>
<div />
</body>
❯ waitForWrapper node_modules/@testing-library/dom/dist/wait-for.js:163:27
❯ node_modules/@testing-library/dom/dist/query-helpers.js:86:33
❯ src/pages/OwnerPage/HeaderBanners/HeaderBanners.test.jsx:163:37
|
|
src/pages/OwnerPage/HeaderBanners/ExceededUploadsAlert/ExceededUploadsAlert.test.jsx > ExceededUploadsAlert > rendering banner > has the correct plan name:
src/pages/OwnerPage/HeaderBanners/ExceededUploadsAlert/ExceededUploadsAlert.test.jsx#L90
TestingLibraryElementError: Unable to find an element with the text: /some-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
<body>
<div>
<div
class="bg-ds-blue-nonary text-ds-gray-octonary p-4 dark:bg-opacity-20 border-l-4 border-ds-blue-quinary"
>
<div
class="flex items-center justify-between pb-2"
>
<h2
class="font-semibold"
>
Upload limit has been reached
</h2>
</div>
<div
class="text-sm md:w-5/6"
>
<p>
This org is currently on the
plan; which includes
free uploads monthly. This month's limit has been reached and the reports will not generate. To resolve this,
<a
class="
font-sans cursor-pointer
hover:underline
focus:ring-2
text-ds-blue-default inline-flex items-center gap-1"
data-cy="upgradeOrgPlan"
data-marketing="upgradeOrgPlan"
href="/plan/gh/codecov/upgrade"
>
upgrade plan
</a>
and you'll have unlimited uploads.
</p>
<div
class="my-6 w-36"
>
<a
class="
flex items-center gap-1
rounded py-1 px-4
transition-colors duration-150 motion-reduce:transition-none
focus:outline-none focus:ring
disabled:cursor-not-allowed
disabled:text-ds-gray-quaternary disabled:border-ds-gray-tertiary disabled:bg-ds-gray-primary
justify-center font-semibold
text-white bg-ds-blue-darker dark:bg-ds-blue-nonary border-ds-blue-quinary
border-solid border shadow
hover:bg-ds-blue-quinary
"
data-cy="upgradeOrgPlan"
data-marketing="upgradeOrgPlan"
href="/plan/gh/codecov/upgrade"
>
Upgrade plan
</a>
</div>
<p>
<span
class="font-semibold"
>
Need help?
</span>
Connect with our sales team today at
<a
class="
font-sans cursor-pointer
hover:underline
focus:ring-2
text-ds-blue-default inline-flex items-center gap-1"
data-cy="sales"
data-marketing="sales"
href="https://about.codecov.io/sales"
target="_blank"
>
sales@codecov.io
<span
class="text-ds-gray-quinary"
>
<svg
class="w-4 h-4"
data-icon=""
data-testid=""
fill="none"
stroke="currentColor"
viewBox="0 0 24 24"
xmlns="http://www.w3.org/2000/svg"
>
<path
d="M10 6H6a2 2 0 00-2 2v10a2 2 0 002 2h10a2 2 0 002-2v-4M14 4h6m0 0v6m0-6L10 14"
stroke-linecap="round"
stroke-linejoin="round"
stroke-width="2"
/>
</svg>
</span>
</a>
</p>
</div>
</div>
</div>
</body>
Ignored nodes: comments, script, style
<body>
<div>
<div
class="bg-ds-blue-nonary text-ds-gray-octonary p-4 dark:bg-opacity-20 border-l-4 border-ds-blue-quinary"
>
<div
class="flex items-center justify-between pb-2"
>
<h2
class="font-semibold"
>
Upload limit has been reached
</h2>
</div>
<div
class="text-sm md:w-5/6"
>
<p>
This org is currently on the
plan; which includes
free uploads monthly. This month's limit has been reached and the reports will not generate. To resolve this,
<a
class="
font-sans cursor-pointer
hover:underline
focus:ring-2
text-ds-blue-default inline-flex items-center gap-1"
data-cy="upgradeOrgPlan"
data-market
|
|
src/pages/OwnerPage/HeaderBanners/ExceededUploadsAlert/ExceededUploadsAlert.test.jsx > ExceededUploadsAlert > rendering banner > has the correct upload limit:
src/pages/OwnerPage/HeaderBanners/ExceededUploadsAlert/ExceededUploadsAlert.test.jsx#L97
TestingLibraryElementError: Unable to find an element with the text: /includes 123 free uploads/. 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>
<div
class="bg-ds-blue-nonary text-ds-gray-octonary p-4 dark:bg-opacity-20 border-l-4 border-ds-blue-quinary"
>
<div
class="flex items-center justify-between pb-2"
>
<h2
class="font-semibold"
>
Upload limit has been reached
</h2>
</div>
<div
class="text-sm md:w-5/6"
>
<p>
This org is currently on the
plan; which includes
free uploads monthly. This month's limit has been reached and the reports will not generate. To resolve this,
<a
class="
font-sans cursor-pointer
hover:underline
focus:ring-2
text-ds-blue-default inline-flex items-center gap-1"
data-cy="upgradeOrgPlan"
data-marketing="upgradeOrgPlan"
href="/plan/gh/codecov/upgrade"
>
upgrade plan
</a>
and you'll have unlimited uploads.
</p>
<div
class="my-6 w-36"
>
<a
class="
flex items-center gap-1
rounded py-1 px-4
transition-colors duration-150 motion-reduce:transition-none
focus:outline-none focus:ring
disabled:cursor-not-allowed
disabled:text-ds-gray-quaternary disabled:border-ds-gray-tertiary disabled:bg-ds-gray-primary
justify-center font-semibold
text-white bg-ds-blue-darker dark:bg-ds-blue-nonary border-ds-blue-quinary
border-solid border shadow
hover:bg-ds-blue-quinary
"
data-cy="upgradeOrgPlan"
data-marketing="upgradeOrgPlan"
href="/plan/gh/codecov/upgrade"
>
Upgrade plan
</a>
</div>
<p>
<span
class="font-semibold"
>
Need help?
</span>
Connect with our sales team today at
<a
class="
font-sans cursor-pointer
hover:underline
focus:ring-2
text-ds-blue-default inline-flex items-center gap-1"
data-cy="sales"
data-marketing="sales"
href="https://about.codecov.io/sales"
target="_blank"
>
sales@codecov.io
<span
class="text-ds-gray-quinary"
>
<svg
class="w-4 h-4"
data-icon=""
data-testid=""
fill="none"
stroke="currentColor"
viewBox="0 0 24 24"
xmlns="http://www.w3.org/2000/svg"
>
<path
d="M10 6H6a2 2 0 00-2 2v10a2 2 0 002 2h10a2 2 0 002-2v-4M14 4h6m0 0v6m0-6L10 14"
stroke-linecap="round"
stroke-linejoin="round"
stroke-width="2"
/>
</svg>
</span>
</a>
</p>
</div>
</div>
</div>
</body>
Ignored nodes: comments, script, style
<body>
<div>
<div
class="bg-ds-blue-nonary text-ds-gray-octonary p-4 dark:bg-opacity-20 border-l-4 border-ds-blue-quinary"
>
<div
class="flex items-center justify-between pb-2"
>
<h2
class="font-semibold"
>
Upload limit has been reached
</h2>
</div>
<div
class="text-sm md:w-5/6"
>
<p>
This org is currently on the
plan; which includes
free uploads monthly. This month's limit has been reached and the reports will not generate. To resolve this,
<a
class="
font-sans cursor-pointer
hover:underline
focus:ring-2
text-ds-blue-default inline-flex items-center gap-1"
data-cy="upgradeOrgPlan"
|
|
src/pages/OwnerPage/HeaderBanners/ReachingUploadLimitAlert/ReachingUploadLimitAlert.test.jsx > ReachingUploadLimitAlert > rendering banner > has the correct plan name:
src/pages/OwnerPage/HeaderBanners/ReachingUploadLimitAlert/ReachingUploadLimitAlert.test.jsx#L92
TestingLibraryElementError: Unable to find an element with the text: /Pro Team/. 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>
<div
class="bg-ds-blue-nonary text-ds-gray-octonary p-4 dark:bg-opacity-20 border-l-4 border-ds-blue-quinary"
>
<div
class="flex items-center justify-between pb-2"
>
<h2
class="font-semibold"
>
Upload limit almost reached
</h2>
</div>
<div
class="text-sm md:w-5/6"
>
<p>
This org is currently on the
plan; which includes
free uploads monthly. This month's limit is nearly reached and the reports will not generate. To resolve this,
<a
class="
font-sans cursor-pointer
hover:underline
focus:ring-2
text-ds-blue-default inline-flex items-center gap-1"
data-cy="upgradeOrgPlan"
data-marketing="upgradeOrgPlan"
href="/plan/gh/codecov/upgrade"
>
upgrade plan
</a>
and you'll have unlimited uploads.
</p>
<div
class="my-6 w-36"
>
<a
class="
flex items-center gap-1
rounded py-1 px-4
transition-colors duration-150 motion-reduce:transition-none
focus:outline-none focus:ring
disabled:cursor-not-allowed
disabled:text-ds-gray-quaternary disabled:border-ds-gray-tertiary disabled:bg-ds-gray-primary
justify-center font-semibold
text-white bg-ds-blue-darker dark:bg-ds-blue-nonary border-ds-blue-quinary
border-solid border shadow
hover:bg-ds-blue-quinary
"
data-cy="upgradeOrgPlan"
data-marketing="upgradeOrgPlan"
href="/plan/gh/codecov/upgrade"
>
Upgrade plan
</a>
</div>
<p>
<span
class="font-semibold"
>
Need help?
</span>
Connect with our sales team today at
<a
class="
font-sans cursor-pointer
hover:underline
focus:ring-2
text-ds-blue-default inline-flex items-center gap-1"
data-cy="sales"
data-marketing="sales"
href="https://about.codecov.io/sales"
target="_blank"
>
sales@codecov.io
<span
class="text-ds-gray-quinary"
>
<svg
class="w-4 h-4"
data-icon=""
data-testid=""
fill="none"
stroke="currentColor"
viewBox="0 0 24 24"
xmlns="http://www.w3.org/2000/svg"
>
<path
d="M10 6H6a2 2 0 00-2 2v10a2 2 0 002 2h10a2 2 0 002-2v-4M14 4h6m0 0v6m0-6L10 14"
stroke-linecap="round"
stroke-linejoin="round"
stroke-width="2"
/>
</svg>
</span>
</a>
</p>
</div>
</div>
</div>
</body>
Ignored nodes: comments, script, style
<body>
<div>
<div
class="bg-ds-blue-nonary text-ds-gray-octonary p-4 dark:bg-opacity-20 border-l-4 border-ds-blue-quinary"
>
<div
class="flex items-center justify-between pb-2"
>
<h2
class="font-semibold"
>
Upload limit almost reached
</h2>
</div>
<div
class="text-sm md:w-5/6"
>
<p>
This org is currently on the
plan; which includes
free uploads monthly. This month's limit is nearly reached and the reports will not generate. To resolve this,
<a
class="
font-sans cursor-pointer
hover:underline
focus:ring-2
text-ds-blue-default inline-flex items-center gap-1"
data-cy="upgradeOrgPlan"
data-marketing
|
|
src/pages/OwnerPage/HeaderBanners/ReachingUploadLimitAlert/ReachingUploadLimitAlert.test.jsx > ReachingUploadLimitAlert > rendering banner > has the correct upload limit:
src/pages/OwnerPage/HeaderBanners/ReachingUploadLimitAlert/ReachingUploadLimitAlert.test.jsx#L98
TestingLibraryElementError: Unable to find an element with the text: /includes 341 free uploads/. 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>
<div
class="bg-ds-blue-nonary text-ds-gray-octonary p-4 dark:bg-opacity-20 border-l-4 border-ds-blue-quinary"
>
<div
class="flex items-center justify-between pb-2"
>
<h2
class="font-semibold"
>
Upload limit almost reached
</h2>
</div>
<div
class="text-sm md:w-5/6"
>
<p>
This org is currently on the
plan; which includes
free uploads monthly. This month's limit is nearly reached and the reports will not generate. To resolve this,
<a
class="
font-sans cursor-pointer
hover:underline
focus:ring-2
text-ds-blue-default inline-flex items-center gap-1"
data-cy="upgradeOrgPlan"
data-marketing="upgradeOrgPlan"
href="/plan/gh/codecov/upgrade"
>
upgrade plan
</a>
and you'll have unlimited uploads.
</p>
<div
class="my-6 w-36"
>
<a
class="
flex items-center gap-1
rounded py-1 px-4
transition-colors duration-150 motion-reduce:transition-none
focus:outline-none focus:ring
disabled:cursor-not-allowed
disabled:text-ds-gray-quaternary disabled:border-ds-gray-tertiary disabled:bg-ds-gray-primary
justify-center font-semibold
text-white bg-ds-blue-darker dark:bg-ds-blue-nonary border-ds-blue-quinary
border-solid border shadow
hover:bg-ds-blue-quinary
"
data-cy="upgradeOrgPlan"
data-marketing="upgradeOrgPlan"
href="/plan/gh/codecov/upgrade"
>
Upgrade plan
</a>
</div>
<p>
<span
class="font-semibold"
>
Need help?
</span>
Connect with our sales team today at
<a
class="
font-sans cursor-pointer
hover:underline
focus:ring-2
text-ds-blue-default inline-flex items-center gap-1"
data-cy="sales"
data-marketing="sales"
href="https://about.codecov.io/sales"
target="_blank"
>
sales@codecov.io
<span
class="text-ds-gray-quinary"
>
<svg
class="w-4 h-4"
data-icon=""
data-testid=""
fill="none"
stroke="currentColor"
viewBox="0 0 24 24"
xmlns="http://www.w3.org/2000/svg"
>
<path
d="M10 6H6a2 2 0 00-2 2v10a2 2 0 002 2h10a2 2 0 002-2v-4M14 4h6m0 0v6m0-6L10 14"
stroke-linecap="round"
stroke-linejoin="round"
stroke-width="2"
/>
</svg>
</span>
</a>
</p>
</div>
</div>
</div>
</body>
Ignored nodes: comments, script, style
<body>
<div>
<div
class="bg-ds-blue-nonary text-ds-gray-octonary p-4 dark:bg-opacity-20 border-l-4 border-ds-blue-quinary"
>
<div
class="flex items-center justify-between pb-2"
>
<h2
class="font-semibold"
>
Upload limit almost reached
</h2>
</div>
<div
class="text-sm md:w-5/6"
>
<p>
This org is currently on the
plan; which includes
free uploads monthly. This month's limit is nearly reached and the reports will not generate. To resolve this,
<a
class="
font-sans cursor-pointer
hover:underline
focus:ring-2
text-ds-blue-default inline-flex items-center gap-1"
data-cy="upgradeOrgPlan"
|
|
Test Runner #1 - Vitest
Process completed with exit code 1.
|
|
Test Runner #6 - Vitest
The job was canceled because "_0" failed.
|
|
Test Runner #6 - Vitest
The operation was canceled.
|
|
Test Runner #5 - Vitest
The job was canceled because "_0" failed.
|
|
Test Runner #5 - Vitest
The operation was canceled.
|
|
Test Runner #2 - Vitest
The job was canceled because "_0" failed.
|
|
Test Runner #2 - Vitest
The operation was canceled.
|
|
Test Runner #3 - Vitest
The job was canceled because "_0" failed.
|
|
src/pages/RepoPage/ActivationAlert/ActivationAlert.test.tsx > ActivationAlert > renders ActivationRequiredAlert when on paid plan and some seats left:
src/pages/RepoPage/ActivationAlert/ActivationAlert.test.tsx#L127
TestingLibraryElementError: Unable to find an element with the text: /ActivationRequiredAlert/. 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>
PaidPlanSeatsTakenAlert
</div>
</body>
Ignored nodes: comments, script, style
<body>
<div>
PaidPlanSeatsTakenAlert
</div>
</body>
❯ waitForWrapper node_modules/@testing-library/dom/dist/wait-for.js:163:27
❯ node_modules/@testing-library/dom/dist/query-helpers.js:86:33
❯ src/pages/RepoPage/ActivationAlert/ActivationAlert.test.tsx:127:50
|
|
Test Runner #3 - Vitest
The operation was canceled.
|
|
Build Self Hosted Image / Build Self Hosted App
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|