Skip to content

implement ResiliencePipeline when using `IsLanguageForgeProjectDataLo… #76

implement ResiliencePipeline when using `IsLanguageForgeProjectDataLo…

implement ResiliencePipeline when using `IsLanguageForgeProjectDataLo… #76

Triggered via push October 7, 2024 06:40
Status Failure
Total duration 2d 2h 6m 40s
Artifacts 2
Set Version
0s
Set Version
Build hgweb  /  publish-hgweb
46s
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
9s
Deploy Production / deploy
Matrix: Deploy Production / verify-published
Generate Release
5s
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 Oct 9, 2024
production

Annotations

14 errors, 111 warnings, and 1 notice
[chromium] › emailWorkflow.test.ts:115:1 › register via new-user invitation email: frontend/tests/emailWorkflow.test.ts#L1
1) [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
1) [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
1) [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
1) [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] › errorHandling.test.ts:61:1 › client-side gql 500 does not break the application: frontend/tests/fixtures.ts#L40
2) [chromium] › errorHandling.test.ts:61:1 › client-side gql 500 does not break the application ── Error: Unexpected response status: 500. (Request URL: https://staging.languagedepot.org/api/graphql. Traceparent: 00-f12b8ecc1d5d45932dcf0129d4896be5-c3facf4fcfe894e6-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)
[chromium] › errorHandling.test.ts:61:1 › client-side gql 500 does not break the application: frontend/tests/errorHandling.test.ts#L70
2) [chromium] › errorHandling.test.ts:61:1 › client-side gql 500 does not break the application ── Error: locator.click: Error: strict mode violation: getByText('Lexbox') resolved to 2 elements: 1) <a class="link" href="mailto:lexbox_support@groups.…>[email protected]</a> aka getByRole('link', { name: '[email protected]' }) 2) <span class="md:leading-none">Lexbox</span> aka getByRole('link', { name: 'Lexbox formerly Language Depot' }) Call log: - waiting for getByText('Lexbox') 68 | await expect(page.locator(':text-matches("Unexpected response:.*(500)", "g")').first()).toBeVisible(); 69 | await page.getByRole('button', { name: 'Dismiss' }).click(); > 70 | await page.getByText('Lexbox').click(); | ^ 71 | await new UserDashboardPage(page).waitFor(); 72 | test.fail(); // Everything up to here passed, but we expect a soft 500 response assertion to ultimately fail the test 73 | }); at /home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/errorHandling.test.ts:70:34
[chromium] › errorHandling.test.ts:61:1 › client-side gql 500 does not break the application: frontend/tests/fixtures.ts#L40
2) [chromium] › errorHandling.test.ts:61:1 › client-side gql 500 does not break the application ── Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Unexpected response status: 500. (Request URL: https://staging.languagedepot.org/api/graphql. Traceparent: 00-a7062397b50c9b17e25333b1ad85e1e6-5aa3d289c349eecc-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)
[chromium] › errorHandling.test.ts:61:1 › client-side gql 500 does not break the application: frontend/tests/errorHandling.test.ts#L70
2) [chromium] › errorHandling.test.ts:61:1 › client-side gql 500 does not break the application ── Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: locator.click: Error: strict mode violation: getByText('Lexbox') resolved to 2 elements: 1) <a class="link" href="mailto:lexbox_support@groups.…>[email protected]</a> aka getByRole('link', { name: '[email protected]' }) 2) <span class="md:leading-none">Lexbox</span> aka getByRole('link', { name: 'Lexbox formerly Language Depot' }) Call log: - waiting for getByText('Lexbox') 68 | await expect(page.locator(':text-matches("Unexpected response:.*(500)", "g")').first()).toBeVisible(); 69 | await page.getByRole('button', { name: 'Dismiss' }).click(); > 70 | await page.getByText('Lexbox').click(); | ^ 71 | await new UserDashboardPage(page).waitFor(); 72 | test.fail(); // Everything up to here passed, but we expect a soft 500 response assertion to ultimately fail the test 73 | }); at /home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/errorHandling.test.ts:70:34
[chromium] › resetProject.test.ts:20:1 › reset project and upload .zip file: frontend/tests/resetProject.test.ts#L35
3) [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/resetProject.test.ts#L75
3) [chromium] › resetProject.test.ts:20:1 › reset project and upload .zip file ─────────────────── Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── 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') 73 | await resetProjectModel.clickNextStepButton('Reset project'); 74 | await resetProjectModel.uploadProjectZipFile(join(tempDir, 'reset-project-test-step-1.zip')); > 75 | await expect(page.getByText('Project successfully reset')).toBeVisible(); | ^ 76 | await page.getByRole('button', { name: 'Close' }).click(); 77 | await resetProjectModel.assertGone(); 78 | at /home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/resetProject.test.ts:75:62
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#L179
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#L184
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#L216
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#L235
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: backend/LexBoxApi/Hub/CrdtProjectChangeHub.cs#L8
Parameter 'loggedInContext' is unread.
Build API / publish-api: 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'
Build API / publish-api: backend/LexBoxApi/Services/HgService.cs#L433
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.
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 'lexAuthService' is unread.
Build API / publish-api
Parameter 'lexBoxDbContext' is unread.
Build API / publish-api
'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'
Build API / publish-api
Parameter 'loggedInContext' is unread.
Slow Test: frontend/[firefox] › resetProject.test.ts#L1
frontend/[firefox] › resetProject.test.ts took 27.7s
Slow Test: frontend/[firefox] › userPage.test.ts#L1
frontend/[firefox] › userPage.test.ts took 25.0s
Slow Test: frontend/[chromium] › userPage.test.ts#L1
frontend/[chromium] › userPage.test.ts took 18.3s
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging: backend/FwLite/MiniLcm/InMemoryApi.cs#L179
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#L184
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#L216
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#L235
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#L433
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, 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#L433
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: backend/LexBoxApi/GraphQL/CustomTypes/IsLanguageForgeProjectDataLoader.cs#L64
Method referencing lambda parameter is not supported LINQ expression. (https://www.mongodb.com/docs/mongodb-analyzer/current/rules/#MALinq2001)
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-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 (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#L179
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#L184
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#L216
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#L235
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#L433
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.
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#L433
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: backend/LexBoxApi/GraphQL/CustomTypes/IsLanguageForgeProjectDataLoader.cs#L64
Method referencing lambda parameter is not supported LINQ expression. (https://www.mongodb.com/docs/mongodb-analyzer/current/rules/#MALinq2001)
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
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/FwLite/MiniLcm/InMemoryApi.cs#L179
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#L184
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#L216
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#L235
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#L433
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
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/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/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#L433
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/LexBoxApi/GraphQL/CustomTypes/IsLanguageForgeProjectDataLoader.cs#L64
Method referencing lambda parameter is not supported LINQ expression. (https://www.mongodb.com/docs/mongodb-analyzer/current/rules/#MALinq2001)
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, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging: backend/FwLite/MiniLcm/InMemoryApi.cs#L179
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#L184
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#L216
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#L235
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#L433
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, 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/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#L433
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, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging: backend/LexBoxApi/GraphQL/CustomTypes/IsLanguageForgeProjectDataLoader.cs#L64
Method referencing lambda parameter is not supported LINQ expression. (https://www.mongodb.com/docs/mongodb-analyzer/current/rules/#MALinq2001)
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.
🎭 Playwright Run Summary
5 failed [chromium] › emailWorkflow.test.ts:115:1 › register via new-user invitation email ────────────── [chromium] › errorHandling.test.ts:61:1 › client-side gql 500 does not break the application ─── [chromium] › resetProject.test.ts:20:1 › reset project and upload .zip file ──────────────────── [firefox] › emailWorkflow.test.ts:115:1 › register via new-user invitation email ─────────────── [firefox] › errorHandling.test.ts:61:1 › client-side gql 500 does not break the application ──── 57 passed (10.9m)

Artifacts

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