Fix hgweb race condition in GetLastCommitTime (#1026) #73
hahn-kevrelease-pipeline.yaml
on: push
Set Version
0s
Build API
/
publish-api
3m 14s
Build UI
/
publish-ui
2m 8s
Matrix: build-hgweb / deploy-hgweb / verify-published
Waiting for pending jobs
Matrix: Deploy Staging / verify-published
Matrix: Integration tests
Matrix: Deploy Production / verify-published
Generate Release
0s
Deployment protection rules
Reviewers, timers, and other rules protecting deployments in this run
| Event | Environments |
|---|---|
hahn-kev
rejected
|
production |
Annotations
19 errors, 113 warnings, and 1 notice
|
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging
Process completed with exit code 1.
|
|
Integration tests (ubuntu-latest, 6) / Playwright tests on ubuntu-latest for Mercurial 6 on staging
Process completed with exit code 2.
|
|
[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:39:35
|
|
[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] › userPage.test.ts:31:1 › can reset password:
frontend/tests/pages/mailPages.ts#L38
4) [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/pages/mailPages.ts#L38
4) [chromium] › userPage.test.ts:31:1 › can reset password ───────────────────────────────────────
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
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
|
|
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging
Process completed with exit code 1.
|
|
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging
Process completed with exit code 2.
|
|
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging
Process completed with exit code 1.
|
|
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging
Process completed with exit code 1.
|
|
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging
Process completed with exit code 1.
|
|
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging
Process completed with exit code 1.
|
|
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/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 (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging:
backend/FixFwData/Program.cs#L1
The variable 'doNothing' is assigned but its value is never used
|
|
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:
backend/LexBoxApi/Services/UserService.cs#L10
Parameter 'lexAuthService' is unread.
|
|
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/Services/UserService.cs#L10
Parameter 'lexAuthService' is unread.
|
|
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:
backend/LexBoxApi/Controllers/IntegrationController.cs#L62
Action method returns undeclared status code '404'
|
|
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.
|
|
Slow Test:
frontend/[firefox] › userPage.test.ts#L1
frontend/[firefox] › userPage.test.ts took 24.1s
|
|
Slow Test:
frontend/[chromium] › resetProject.test.ts#L1
frontend/[chromium] › resetProject.test.ts took 22.5s
|
|
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging
The support for python 2.7 was removed on June 19, 2023. Related issue: https://github.com/actions/setup-python/issues/672
|
|
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/FixFwData/Program.cs#L1
The variable 'doNothing' is assigned but its value is never used
|
|
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:
backend/LexBoxApi/Services/UserService.cs#L10
Parameter 'lexAuthService' is unread.
|
|
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/Services/UserService.cs#L10
Parameter 'lexAuthService' is unread.
|
|
|
|
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:
backend/LexBoxApi/Controllers/IntegrationController.cs#L62
Action method returns undeclared status code '404'
|
|
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, 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/FixFwData/Program.cs#L1
The variable 'doNothing' is assigned but its value is never used
|
|
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/LexBoxApi/Services/UserService.cs#L10
Parameter 'lexAuthService' is unread.
|
|
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/Services/UserService.cs#L10
Parameter 'lexAuthService' is unread.
|
|
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, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging:
backend/LexBoxApi/Controllers/IntegrationController.cs#L62
Action method returns undeclared status code '404'
|
|
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, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging:
backend/FixFwData/Program.cs#L1
The variable 'doNothing' is assigned but its value is never used
|
|
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/LexBoxApi/Services/UserService.cs#L10
Parameter 'lexAuthService' is unread.
|
|
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/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/Services/UserService.cs#L10
Parameter 'lexAuthService' is unread.
|
|
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.
|
|
|
|
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging:
backend/LexBoxApi/Controllers/IntegrationController.cs#L62
Action method returns undeclared status code '404'
|
|
🎭 Playwright Run Summary
8 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] › userPage.test.ts:31:1 › can reset password ────────────────────────────────────────
[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 ─────────────────────
3 flaky
[chromium] › errorHandling.test.ts:141:1 › page load 403 on home page is redirected to login ───
[firefox] › emailWorkflow.test.ts:28:1 › register, verify, update, verify email address ────────
[firefox] › i18n.test.ts:30:1 › late subscription to locale works ──────────────────────────────
51 passed (14.2m)
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
dotnet-unit-test-results
|
2.76 KB |
|
|
playwright-traces-ubuntu-latest-hg-6
|
382 MB |
|