Skip to content

Merge remote-tracking branch 'origin/develop' #66

Merge remote-tracking branch 'origin/develop'

Merge remote-tracking branch 'origin/develop' #66

Triggered via push June 20, 2024 16:16
Status Failure
Total duration 17d 16h 34m 48s
Artifacts 1
Set Version
0s
Set Version
Build hgweb  /  publish-hgweb
1m 3s
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
12s
Deploy Staging / deploy
Matrix: Deploy Staging / verify-published
Matrix: Integration tests
Deploy Production  /  deploy
0s
Deploy Production / deploy
Matrix: Deploy Production / verify-published
Generate Release
0s
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
rejected Jul 8, 2024
production

Annotations

15 errors, 103 warnings, and 1 notice
[chromium] › emailWorkflow.test.ts:28:1 › register: frontend/tests/emailWorkflow.test.ts#L1
1) [chromium] › emailWorkflow.test.ts:28:1 › register, verify, update, verify email address ────── Test timeout of 120000ms exceeded.
[chromium] › emailWorkflow.test.ts:28:1 › register: frontend/tests/pages/authenticatedBasePage.ts#L19
1) [chromium] › emailWorkflow.test.ts:28:1 › register, verify, update, verify email address ────── Error: locator.click: Test timeout of 120000ms exceeded. Call log: - waiting for locator('.breadcrumbs').getByRole('link', { name: 'Home' }) at pages/authenticatedBasePage.ts:19 17 | 18 | clickHome(): Promise<void> { > 19 | return this.page.locator('.breadcrumbs').getByRole('link', {name: 'Home'}).click(); | ^ 20 | } 21 | } 22 | at UserAccountSettingsPage.clickHome (/home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/pages/authenticatedBasePage.ts:19:80) at /home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/emailWorkflow.test.ts:48:18
[chromium] › emailWorkflow.test.ts:28:1 › register: frontend/tests/emailWorkflow.test.ts#L1
1) [chromium] › emailWorkflow.test.ts:28:1 › register, verify, update, verify email address ────── Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Test timeout of 120000ms exceeded.
[chromium] › emailWorkflow.test.ts:28:1 › register: frontend/tests/pages/authenticatedBasePage.ts#L19
1) [chromium] › emailWorkflow.test.ts:28:1 › register, verify, update, verify email address ────── Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: locator.click: Test timeout of 120000ms exceeded. Call log: - waiting for locator('.breadcrumbs').getByRole('link', { name: 'Home' }) at pages/authenticatedBasePage.ts:19 17 | 18 | clickHome(): Promise<void> { > 19 | return this.page.locator('.breadcrumbs').getByRole('link', {name: 'Home'}).click(); | ^ 20 | } 21 | } 22 | at UserAccountSettingsPage.clickHome (/home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/pages/authenticatedBasePage.ts:19:80) at /home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/emailWorkflow.test.ts:48:18
[chromium] › errorHandling.test.ts:141:1 › page load 403 on home page is redirected to login: frontend/tests/errorHandling.test.ts#L1
2) [chromium] › errorHandling.test.ts:141:1 › page load 403 on home page is redirected to login ── Test timeout of 120000ms exceeded.
[chromium] › errorHandling.test.ts:141:1 › page load 403 on home page is redirected to login: frontend/tests/errorHandling.test.ts#L167
2) [chromium] › errorHandling.test.ts:141:1 › page load 403 on home page is redirected to login ── Error: page.waitForResponse: Test timeout of 120000ms exceeded. =========================== logs =========================== waiting for response "/api/graphql" ============================================================ 165 | await page.context().addCookies([{name: testEnv.authCookieName, value: forgotPasswordJwt, url: testEnv.serverBaseUrl}]); 166 | > 167 | const responsePromise = page.waitForResponse('/api/graphql'); | ^ 168 | await userAccountPage.clickHome(); 169 | const response = await responsePromise; 170 | expect(response.status()).toBe(403); at /home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/errorHandling.test.ts:167:32
[chromium] › errorHandling.test.ts:141:1 › page load 403 on home page is redirected to login: frontend/tests/pages/authenticatedBasePage.ts#L19
2) [chromium] › errorHandling.test.ts:141:1 › page load 403 on home page is redirected to login ── Error: locator.click: Test timeout of 120000ms exceeded. Call log: - waiting for locator('.breadcrumbs').getByRole('link', { name: 'Home' }) at pages/authenticatedBasePage.ts:19 17 | 18 | clickHome(): Promise<void> { > 19 | return this.page.locator('.breadcrumbs').getByRole('link', {name: 'Home'}).click(); | ^ 20 | } 21 | } 22 | at UserAccountSettingsPage.clickHome (/home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/pages/authenticatedBasePage.ts:19:80) at /home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/errorHandling.test.ts:168:25
[chromium] › errorHandling.test.ts:141:1 › page load 403 on home page is redirected to login: frontend/tests/pages/mailPages.ts#L38
2) [chromium] › errorHandling.test.ts:141:1 › page load 403 on home page is redirected to login ── 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/errorHandling.test.ts:155:37
[chromium] › userPage.test.ts:31:1 › can reset password: frontend/tests/pages/mailPages.ts#L38
3) [chromium] › userPage.test.ts:31:1 › can reset password ─────────────────────────────────────── Error: Failed to find email: Your password was changed (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/userPage.test.ts:50:37
[chromium] › userPage.test.ts:31:1 › can reset password: frontend/tests/utils/authHelpers.ts#L16
3) [chromium] › userPage.test.ts:31:1 › can reset password ─────────────────────────────────────── Error: expect(received).toBeTruthy() Received: false at utils/authHelpers.ts:16 14 | } 15 | const response = await api.post(`${serverBaseUrl}/api/login`, {data: loginData}); > 16 | expect(response.ok()).toBeTruthy(); | ^ 17 | } 18 | 19 | export async function logout(page: Page): Promise<LoginPage> { at loginAs (/home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/utils/authHelpers.ts:16:25) at Object.tempUser (/home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/fixtures.ts:87:5)
Deploy Production / deploy
The deployment was rejected or didn't satisfy other protection rules.
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/MiniLcm/InMemoryApi.cs#L195
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/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/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L219
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/FwDataMiniLcmBridge/LcmUtils/LcmThreadedProgress.cs#L10
The event 'LcmThreadedProgress.Canceling' is never used
Build API / publish-api: backend/FwDataMiniLcmBridge/Api/UpdateProxy/UpdateSenseProxy.cs#L43
Observe the awaitable result of this method call by awaiting it, assigning to a variable, or passing it to another method (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD110.md)
Build API / publish-api: backend/FwDataMiniLcmBridge/Api/UpdateProxy/UpdateEntryProxy.cs#L38
Observe the awaitable result of this method call by awaiting it, assigning to a variable, or passing it to another method (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD110.md)
Build API / publish-api: backend/LfClassicData/LfClassicLexboxApi.cs#L170
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
Found version-specific or distribution-specific runtime identifier(s): debian-x64, fedora-x64, opensuse-x64, rhel-x64, win7-arm, win7-x64, win7-x86. Affected libraries: Libuv. In .NET 8.0 and higher, assets for version-specific and distribution-specific runtime identifiers will not be found by default. See https://aka.ms/dotnet/rid-usage for details.
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
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 '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 'hgService' is unread.
Build API / publish-api
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
No files were found with the provided path: ./test-results. No artifacts will be uploaded.
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging: backend/MiniLcm/InMemoryApi.cs#L195
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/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/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L219
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#L170
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
Found version-specific or distribution-specific runtime identifier(s): debian-x64, fedora-x64, opensuse-x64, rhel-x64, win7-arm, win7-x64, win7-x86. Affected libraries: Libuv. In .NET 8.0 and higher, assets for version-specific and distribution-specific runtime identifiers will not be found by default. See https://aka.ms/dotnet/rid-usage for details.
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#L170
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#L308
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/MiniLcm/InMemoryApi.cs#L195
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/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/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L219
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#L170
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
Found version-specific or distribution-specific runtime identifier(s): debian-x64, fedora-x64, opensuse-x64, rhel-x64, win7-arm, win7-x64, win7-x86. Affected libraries: Libuv. In .NET 8.0 and higher, assets for version-specific and distribution-specific runtime identifiers will not be found by default. See https://aka.ms/dotnet/rid-usage for details.
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#L170
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#L308
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#L27
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/MiniLcm/InMemoryApi.cs#L195
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/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/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L219
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#L170
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
Found version-specific or distribution-specific runtime identifier(s): debian-x64, fedora-x64, opensuse-x64, rhel-x64, win7-arm, win7-x64, win7-x86. Affected libraries: Libuv. In .NET 8.0 and higher, assets for version-specific and distribution-specific runtime identifiers will not be found by default. See https://aka.ms/dotnet/rid-usage for details.
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#L170
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#L308
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/[firefox] › userPage.test.ts#L1
frontend/[firefox] › userPage.test.ts took 23.3s
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging: backend/MiniLcm/InMemoryApi.cs#L195
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/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/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L219
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
Found version-specific or distribution-specific runtime identifier(s): debian-x64, fedora-x64, opensuse-x64, rhel-x64, win7-arm, win7-x64, win7-x86. Affected libraries: Libuv. In .NET 8.0 and higher, assets for version-specific and distribution-specific runtime identifiers will not be found by default. See https://aka.ms/dotnet/rid-usage for details.
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging: backend/LfClassicData/LfClassicLexboxApi.cs#L170
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#L170
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#L308
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.
🎭 Playwright Run Summary
5 failed [chromium] › emailWorkflow.test.ts:28:1 › register, verify, update, verify email address ─────── [chromium] › errorHandling.test.ts:141:1 › page load 403 on home page is redirected to login ─── [chromium] › userPage.test.ts:31:1 › can reset password ──────────────────────────────────────── [firefox] › emailWorkflow.test.ts:28:1 › register, verify, update, verify email address ──────── [firefox] › errorHandling.test.ts:141:1 › page load 403 on home page is redirected to login ──── 3 flaky [firefox] › adminPage.test.ts:6:1 › can navigate to project page ─────────────────────────────── [firefox] › emailWorkflow.test.ts:78:1 › forgot password ─────────────────────────────────────── [firefox] › emailWorkflow.test.ts:115:1 › register via new-user invitation email ─────────────── 54 passed (18.8m)

Artifacts

Produced during runtime
Name Size
playwright-traces-ubuntu-latest-hg-6 Expired
284 MB