Skip to content

increase memory limits for lexbox api, 1gb for prod #74

increase memory limits for lexbox api, 1gb for prod

increase memory limits for lexbox api, 1gb for prod #74

Triggered via push August 26, 2024 04:22
Status Failure
Total duration 30m 23s
Artifacts 2
Set Version
0s
Set Version
Build hgweb  /  publish-hgweb
37s
Build hgweb / publish-hgweb
build-hgweb  /  ...  /  deploy
build-hgweb / deploy-hgweb / deploy
Matrix: build-hgweb / deploy-hgweb / verify-published
Waiting for pending jobs
Deploy Staging  /  deploy
8s
Deploy Staging / deploy
Matrix: Deploy Staging / verify-published
Matrix: Integration tests
Deploy Production  /  deploy
17s
Deploy Production / deploy
Matrix: Deploy Production / verify-published
Generate Release
2s
Generate Release
Fit to window
Zoom out
Zoom in

Deployment protection rules

Reviewers, timers, and other rules protecting deployments in this run
Event Environments Comment
hahn-kev
approved Aug 26, 2024
production

Annotations

17 errors, 111 warnings, and 1 notice
[chromium] β€Ί emailWorkflow.test.ts:28:1 β€Ί register: frontend/tests/pages/mailPages.ts#L38
1) [chromium] β€Ί emailWorkflow.test.ts:28:1 β€Ί register, verify, update, verify email address ────── Error: Failed to find email: Verify your e-mail address (0) Timeout 10000ms exceeded while waiting on the predicate at pages/mailPages.ts:38 36 | } 37 | await email.click(); > 38 | }, `Failed to find email: ${subject} (${index})`).toPass({timeout: 10_000}); // This auto-retries on a reasonable schedule | ^ 39 | return await this.getEmailPage().waitFor(); 40 | } 41 | } at MailinatorInboxPage.openEmail (/home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/pages/mailPages.ts:38:55) at /home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/emailWorkflow.test.ts:39:35
[chromium] β€Ί emailWorkflow.test.ts:28:1 β€Ί register: frontend/tests/pages/mailPages.ts#L38
1) [chromium] β€Ί emailWorkflow.test.ts:28:1 β€Ί register, verify, update, verify email address ────── Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Failed to find email: Verify your e-mail address (0) Timeout 10000ms exceeded while waiting on the predicate at pages/mailPages.ts:38 36 | } 37 | await email.click(); > 38 | }, `Failed to find email: ${subject} (${index})`).toPass({timeout: 10_000}); // This auto-retries on a reasonable schedule | ^ 39 | return await this.getEmailPage().waitFor(); 40 | } 41 | } at MailinatorInboxPage.openEmail (/home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/pages/mailPages.ts:38:55) at /home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/emailWorkflow.test.ts:63:31
[chromium] β€Ί emailWorkflow.test.ts:78:1 β€Ί forgot password: frontend/tests/pages/mailPages.ts#L38
2) [chromium] β€Ί emailWorkflow.test.ts:78:1 β€Ί forgot password ───────────────────────────────────── Error: Failed to find email: Forgot your password? (0) Timeout 10000ms exceeded while waiting on the predicate at pages/mailPages.ts:38 36 | } 37 | await email.click(); > 38 | }, `Failed to find email: ${subject} (${index})`).toPass({timeout: 10_000}); // This auto-retries on a reasonable schedule | ^ 39 | return await this.getEmailPage().waitFor(); 40 | } 41 | } at MailinatorInboxPage.openEmail (/home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/pages/mailPages.ts:38:55) at /home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/emailWorkflow.test.ts:89:37
[chromium] β€Ί emailWorkflow.test.ts:78:1 β€Ί forgot password: frontend/tests/pages/mailPages.ts#L38
2) [chromium] β€Ί emailWorkflow.test.ts:78:1 β€Ί forgot password ───────────────────────────────────── Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Failed to find email: Forgot your password? (0) Timeout 10000ms exceeded while waiting on the predicate at pages/mailPages.ts:38 36 | } 37 | await email.click(); > 38 | }, `Failed to find email: ${subject} (${index})`).toPass({timeout: 10_000}); // This auto-retries on a reasonable schedule | ^ 39 | return await this.getEmailPage().waitFor(); 40 | } 41 | } at MailinatorInboxPage.openEmail (/home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/pages/mailPages.ts:38:55) at /home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/emailWorkflow.test.ts:89:37
[chromium] β€Ί emailWorkflow.test.ts:115:1 β€Ί register via new-user invitation email: frontend/tests/emailWorkflow.test.ts#L1
3) [chromium] β€Ί emailWorkflow.test.ts:115:1 β€Ί register via new-user invitation email ───────────── Test timeout of 80000ms exceeded.
[chromium] β€Ί emailWorkflow.test.ts:115:1 β€Ί register via new-user invitation email: frontend/tests/emailWorkflow.test.ts#L130
3) [chromium] β€Ί emailWorkflow.test.ts:115:1 β€Ί register via new-user invitation email ───────────── Error: locator.click: Test timeout of 80000ms exceeded. Call log: - waiting for locator('dialog.modal').filter({ hasText: 'Add or invite a Member to this project' }).getByRole('button', { name: /Add Member|Add or invite Member/ }) 128 | await addMemberModal.selectEditorRole(); 129 | await addMemberModal.inviteCheckbox.check(); > 130 | await addMemberModal.submitButton.click(); | ^ 131 | await page.locator(':text("has been sent an invitation email")').waitFor(); 132 | 133 | // Check invite link returnTo is relative path, not absolute at /home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/emailWorkflow.test.ts:130:37
[chromium] β€Ί emailWorkflow.test.ts:115:1 β€Ί register via new-user invitation email: frontend/tests/emailWorkflow.test.ts#L1
3) [chromium] β€Ί emailWorkflow.test.ts:115:1 β€Ί register via new-user invitation email ───────────── Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Test timeout of 80000ms exceeded.
[chromium] β€Ί emailWorkflow.test.ts:115:1 β€Ί register via new-user invitation email: frontend/tests/emailWorkflow.test.ts#L130
3) [chromium] β€Ί emailWorkflow.test.ts:115:1 β€Ί register via new-user invitation email ───────────── Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: locator.click: Test timeout of 80000ms exceeded. Call log: - waiting for locator('dialog.modal').filter({ hasText: 'Add or invite a Member to this project' }).getByRole('button', { name: /Add Member|Add or invite Member/ }) 128 | await addMemberModal.selectEditorRole(); 129 | await addMemberModal.inviteCheckbox.check(); > 130 | await addMemberModal.submitButton.click(); | ^ 131 | await page.locator(':text("has been sent an invitation email")').waitFor(); 132 | 133 | // Check invite link returnTo is relative path, not absolute at /home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/emailWorkflow.test.ts:130:37
[chromium] β€Ί resetProject.test.ts:20:1 β€Ί reset project and upload .zip file: frontend/tests/resetProject.test.ts#L35
4) [chromium] β€Ί resetProject.test.ts:20:1 β€Ί reset project and upload .zip file ─────────────────── Error: Timed out 5000ms waiting for expect(locator).toBeVisible() Locator: getByText('Project successfully reset') Expected: visible Received: <element(s) not found> Call log: - expect.toBeVisible with timeout 5000ms - waiting for getByText('Project successfully reset') 33 | await resetProjectModel.clickNextStepButton('Reset project'); 34 | await resetProjectModel.uploadProjectZipFile('tests/data/test-project-one-commit.zip'); > 35 | await expect(page.getByText('Project successfully reset')).toBeVisible(); | ^ 36 | await page.getByRole('button', { name: 'Close' }).click(); 37 | await resetProjectModel.assertGone(); 38 | at /home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/resetProject.test.ts:35:62
[chromium] β€Ί resetProject.test.ts:20:1 β€Ί reset project and upload .zip file: frontend/tests/fixtures.ts#L40
4) [chromium] β€Ί resetProject.test.ts:20:1 β€Ί reset project and upload .zip file ─────────────────── Error: Unexpected response status: 500. (Request URL: https://staging.languagedepot.org/api/project/upload-zip/test-reset-project-and-upload-zip-file-fc95993af9013e6c5450-6e85e0716fb6a9bfa2aa-5f0f32bc/bac21fd02b944a38bc6fa3aeb384d3d5. Traceparent: 00-857cc59c2787332c3a47269bc5397873-28debd9b6218116b-01.) expect(received).toBeLessThan(expected) Expected: < 500 Received: 500 at fixtures.ts:40 38 | const url = response.request().url(); 39 | const unexpectedResponseMessage = `Unexpected response status: ${status}. (Request URL: ${url}. Traceparent: ${traceparent}.)`; > 40 | expect.soft(response.status(), unexpectedResponseMessage).toBeLessThan(500); | ^ 41 | if (response.request().isNavigationRequest()) { 42 | expect.soft(response.status(), unexpectedResponseMessage).toBeLessThan(400); 43 | } at BrowserContext.<anonymous> (/home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/fixtures.ts:40:63)
Build API / publish-api: backend/FixFwData/Program.cs#L1
The variable 'doNothing' is assigned but its value is never used
Build API / publish-api: backend/FwLite/MiniLcm/InMemoryApi.cs#L177
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Build API / publish-api: backend/FwLite/MiniLcm/InMemoryApi.cs#L182
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Build API / publish-api: backend/FwLite/MiniLcm/InMemoryApi.cs#L214
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Build API / publish-api: backend/FwLite/MiniLcm/InMemoryApi.cs#L233
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Build API / publish-api: backend/LfClassicData/LfClassicLexboxApi.cs#L62
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Build API / publish-api: backend/LfClassicData/LfClassicLexboxApi.cs#L67
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Build API / publish-api: backend/LfClassicData/LfClassicLexboxApi.cs#L201
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Build API / publish-api: backend/LexData/SeedingData.cs#L18
Parameter 'logger' is unread.
Build API / publish-api: backend/LexBoxApi/Services/UserService.cs#L10
Parameter 'lexAuthService' is unread.
Build API / publish-api
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Build API / publish-api
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Build API / publish-api
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Build API / publish-api
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Build API / publish-api
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Build API / publish-api
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Build API / publish-api
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Build API / publish-api
Parameter 'logger' is unread.
Build API / publish-api
Parameter 'lexAuthService' is unread.
Build API / publish-api
Parameter 'hgService' is unread.
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging: backend/FwLite/MiniLcm/InMemoryApi.cs#L177
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging: backend/FwLite/MiniLcm/InMemoryApi.cs#L182
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging: backend/FwLite/MiniLcm/InMemoryApi.cs#L214
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging: backend/FwLite/MiniLcm/InMemoryApi.cs#L233
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging: backend/LfClassicData/LfClassicLexboxApi.cs#L62
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging: backend/LfClassicData/LfClassicLexboxApi.cs#L67
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging: backend/LfClassicData/LfClassicLexboxApi.cs#L201
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging: backend/Testing/Fixtures/Tests/ServicesFixtureTests.cs#L8
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging: backend/Testing/Fixtures/Tests/ServicesFixtureTests.cs#L8
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging: backend/LfClassicData/LfClassicLexboxApi.cs#L62
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging: backend/LfClassicData/LfClassicLexboxApi.cs#L67
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging: backend/LfClassicData/LfClassicLexboxApi.cs#L201
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging: backend/LexBoxApi/Auth/JwtTicketDataFormat.cs#L122
'JwtBearerOptions.SecurityTokenValidators' is obsolete: 'SecurityTokenValidators is no longer used by default. Use TokenHandlers instead. To continue using SecurityTokenValidators, set UseSecurityTokenValidators to true. See https://aka.ms/aspnetcore8/security-token-changes'
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging: backend/LexBoxApi/Services/HgService.cs#L374
The switch expression does not handle some values of its input type (it is not exhaustive) involving an unnamed enum value. For example, the pattern '(LexBoxApi.Services.RepoEmptyState)2' is not covered.
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging: backend/FwLite/MiniLcm/InMemoryApi.cs#L177
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging: backend/FwLite/MiniLcm/InMemoryApi.cs#L182
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging: backend/FwLite/MiniLcm/InMemoryApi.cs#L214
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging: backend/FwLite/MiniLcm/InMemoryApi.cs#L233
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging: backend/LfClassicData/LfClassicLexboxApi.cs#L62
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging: backend/LfClassicData/LfClassicLexboxApi.cs#L67
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging: backend/LfClassicData/LfClassicLexboxApi.cs#L201
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging: backend/Testing/Fixtures/Tests/ServicesFixtureTests.cs#L8
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging: backend/Testing/Fixtures/Tests/ServicesFixtureTests.cs#L8
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging: backend/LfClassicData/LfClassicLexboxApi.cs#L62
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging: backend/LfClassicData/LfClassicLexboxApi.cs#L67
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging: backend/LfClassicData/LfClassicLexboxApi.cs#L201
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging: backend/LexBoxApi/Auth/JwtTicketDataFormat.cs#L122
'JwtBearerOptions.SecurityTokenValidators' is obsolete: 'SecurityTokenValidators is no longer used by default. Use TokenHandlers instead. To continue using SecurityTokenValidators, set UseSecurityTokenValidators to true. See https://aka.ms/aspnetcore8/security-token-changes'
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging: backend/LexBoxApi/Services/HgService.cs#L374
The switch expression does not handle some values of its input type (it is not exhaustive) involving an unnamed enum value. For example, the pattern '(LexBoxApi.Services.RepoEmptyState)2' is not covered.
Slow Test: frontend/[chromium] β€Ί errorHandling.test.ts#L1
frontend/[chromium] β€Ί errorHandling.test.ts took 29.5s
Slow Test: frontend/[firefox] β€Ί userPage.test.ts#L1
frontend/[firefox] β€Ί userPage.test.ts took 23.8s
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging: backend/FwLite/MiniLcm/InMemoryApi.cs#L177
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging: backend/FwLite/MiniLcm/InMemoryApi.cs#L182
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging: backend/FwLite/MiniLcm/InMemoryApi.cs#L214
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging: backend/FwLite/MiniLcm/InMemoryApi.cs#L233
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging: backend/LfClassicData/LfClassicLexboxApi.cs#L62
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging: backend/LfClassicData/LfClassicLexboxApi.cs#L67
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging: backend/LfClassicData/LfClassicLexboxApi.cs#L201
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging: backend/LfClassicData/LfClassicLexboxApi.cs#L62
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging: backend/LfClassicData/LfClassicLexboxApi.cs#L67
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging: backend/LfClassicData/LfClassicLexboxApi.cs#L201
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging: backend/LexBoxApi/Auth/JwtTicketDataFormat.cs#L122
'JwtBearerOptions.SecurityTokenValidators' is obsolete: 'SecurityTokenValidators is no longer used by default. Use TokenHandlers instead. To continue using SecurityTokenValidators, set UseSecurityTokenValidators to true. See https://aka.ms/aspnetcore8/security-token-changes'
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging: backend/LexBoxApi/Services/HgService.cs#L374
The switch expression does not handle some values of its input type (it is not exhaustive) involving an unnamed enum value. For example, the pattern '(LexBoxApi.Services.RepoEmptyState)2' is not covered.
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging: backend/Testing/Fixtures/Tests/ServicesFixtureTests.cs#L8
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging: backend/Testing/Fixtures/Tests/ServicesFixtureTests.cs#L8
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging: backend/FwLite/MiniLcm/InMemoryApi.cs#L177
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging: backend/FwLite/MiniLcm/InMemoryApi.cs#L182
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging: backend/FwLite/MiniLcm/InMemoryApi.cs#L214
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging: backend/FwLite/MiniLcm/InMemoryApi.cs#L233
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging: backend/LfClassicData/LfClassicLexboxApi.cs#L62
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging: backend/LfClassicData/LfClassicLexboxApi.cs#L67
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging: backend/LfClassicData/LfClassicLexboxApi.cs#L201
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging: backend/LfClassicData/LfClassicLexboxApi.cs#L62
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging: backend/LfClassicData/LfClassicLexboxApi.cs#L67
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging: backend/LfClassicData/LfClassicLexboxApi.cs#L201
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging: backend/LexBoxApi/Auth/JwtTicketDataFormat.cs#L122
'JwtBearerOptions.SecurityTokenValidators' is obsolete: 'SecurityTokenValidators is no longer used by default. Use TokenHandlers instead. To continue using SecurityTokenValidators, set UseSecurityTokenValidators to true. See https://aka.ms/aspnetcore8/security-token-changes'
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging: backend/LexBoxApi/Services/HgService.cs#L374
The switch expression does not handle some values of its input type (it is not exhaustive) involving an unnamed enum value. For example, the pattern '(LexBoxApi.Services.RepoEmptyState)2' is not covered.
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
🎭 Playwright Run Summary
9 failed [chromium] β€Ί emailWorkflow.test.ts:28:1 β€Ί register, verify, update, verify email address ─────── [chromium] β€Ί emailWorkflow.test.ts:78:1 β€Ί forgot password ────────────────────────────────────── [chromium] β€Ί emailWorkflow.test.ts:115:1 β€Ί register via new-user invitation email ────────────── [chromium] β€Ί resetProject.test.ts:20:1 β€Ί reset project and upload .zip file ──────────────────── [firefox] β€Ί emailWorkflow.test.ts:28:1 β€Ί register, verify, update, verify email address ──────── [firefox] β€Ί emailWorkflow.test.ts:78:1 β€Ί forgot password ─────────────────────────────────────── [firefox] β€Ί emailWorkflow.test.ts:115:1 β€Ί register via new-user invitation email ─────────────── [firefox] β€Ί errorHandling.test.ts:141:1 β€Ί page load 403 on home page is redirected to login ──── [firefox] β€Ί resetProject.test.ts:20:1 β€Ί reset project and upload .zip file ───────────────────── 1 flaky [chromium] β€Ί userPage.test.ts:31:1 β€Ί can reset password ──────────────────────────────────────── 52 passed (12.8m)

Artifacts

Produced during runtime
Name Size
dotnet-unit-test-results
2.75 KB
playwright-traces-ubuntu-latest-hg-6
345 MB