Skip to content

limit the build scope when running integration tests to avoid buildin… #71

limit the build scope when running integration tests to avoid buildin…

limit the build scope when running integration tests to avoid buildin… #71

Triggered via push July 31, 2024 06:51
Status Failure
Total duration 1h 3m 27s
Artifacts 1
Set Version
0s
Set Version
Build hgweb  /  publish-hgweb
45s
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
17s
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 31, 2024
production

integration tests not running

Annotations

23 errors, 95 warnings, and 1 notice
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging
To build this project, the following workloads must be installed: maui-tizen
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging
To install these workloads, run the following command: dotnet workload restore
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging
To build this project, the following workloads must be installed: maui-tizen
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging
To install these workloads, run the following command: dotnet workload restore
[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.waitFor: Test timeout of 80000ms exceeded. Call log: - waiting for locator(':text("has been sent an invitation email")') to be visible 128 | await addMemberModal.selectEditorRole(); 129 | await addMemberModal.submitButton.click(); > 130 | await page.locator(':text("has been sent an invitation email")').waitFor(); | ^ 131 | 132 | // Check invite link returnTo is relative path, not absolute 133 | const inboxPage = await getInbox(page, uuid).goto(); at /home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/emailWorkflow.test.ts:130:68
[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.waitFor: Test timeout of 80000ms exceeded. Call log: - waiting for locator(':text("has been sent an invitation email")') to be visible 128 | await addMemberModal.selectEditorRole(); 129 | await addMemberModal.submitButton.click(); > 130 | await page.locator(':text("has been sent an invitation email")').waitFor(); | ^ 131 | 132 | // Check invite link returnTo is relative path, not absolute 133 | const inboxPage = await getInbox(page, uuid).goto(); at /home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/emailWorkflow.test.ts:130:68
[firefox] › emailWorkflow.test.ts:28:1 › register: frontend/tests/pages/mailPages.ts#L38
2) [firefox] › 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
[firefox] › emailWorkflow.test.ts:28:1 › register: frontend/tests/pages/mailPages.ts#L38
2) [firefox] › emailWorkflow.test.ts:28:1 › register, verify, update, verify email address ─────── Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Failed to find email: Verify your e-mail address (0) Timeout 10000ms exceeded while waiting on the predicate at pages/mailPages.ts:38 36 | } 37 | await email.click(); > 38 | }, `Failed to find email: ${subject} (${index})`).toPass({timeout: 10_000}); // This auto-retries on a reasonable schedule | ^ 39 | return await this.getEmailPage().waitFor(); 40 | } 41 | } at MailinatorInboxPage.openEmail (/home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/pages/mailPages.ts:38:55) at /home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/emailWorkflow.test.ts:63:31
[firefox] › emailWorkflow.test.ts:115:1 › register via new-user invitation email: frontend/tests/emailWorkflow.test.ts#L1
3) [firefox] › emailWorkflow.test.ts:115:1 › register via new-user invitation email ────────────── Test timeout of 80000ms exceeded.
[firefox] › emailWorkflow.test.ts:115:1 › register via new-user invitation email: frontend/tests/emailWorkflow.test.ts#L130
3) [firefox] › emailWorkflow.test.ts:115:1 › register via new-user invitation email ────────────── Error: locator.waitFor: Test timeout of 80000ms exceeded. Call log: - waiting for locator(':text("has been sent an invitation email")') to be visible 128 | await addMemberModal.selectEditorRole(); 129 | await addMemberModal.submitButton.click(); > 130 | await page.locator(':text("has been sent an invitation email")').waitFor(); | ^ 131 | 132 | // Check invite link returnTo is relative path, not absolute 133 | const inboxPage = await getInbox(page, uuid).goto(); at /home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/emailWorkflow.test.ts:130:68
[firefox] › emailWorkflow.test.ts:115:1 › register via new-user invitation email: frontend/tests/emailWorkflow.test.ts#L1
3) [firefox] › emailWorkflow.test.ts:115:1 › register via new-user invitation email ────────────── Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Test timeout of 80000ms exceeded.
[firefox] › emailWorkflow.test.ts:115:1 › register via new-user invitation email: frontend/tests/emailWorkflow.test.ts#L130
3) [firefox] › emailWorkflow.test.ts:115:1 › register via new-user invitation email ────────────── Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: locator.waitFor: Test timeout of 80000ms exceeded. Call log: - waiting for locator(':text("has been sent an invitation email")') to be visible 128 | await addMemberModal.selectEditorRole(); 129 | await addMemberModal.submitButton.click(); > 130 | await page.locator(':text("has been sent an invitation email")').waitFor(); | ^ 131 | 132 | // Check invite link returnTo is relative path, not absolute 133 | const inboxPage = await getInbox(page, uuid).goto(); at /home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/emailWorkflow.test.ts:130:68
Deploy Production / deploy
The deployment was rejected or didn't satisfy other protection rules.
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: backend/LexBoxApi/Jobs/CleanupResetBackupJob.cs#L7
Parameter 'hgService' 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.
Build API / publish-api: backend/FixFwData/Program.cs#L1
The variable 'doNothing' is assigned but its value is never used
Build API / publish-api
No files were found with the provided path: ./test-results. No artifacts will be uploaded.
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging
Could not find any files for ./test-results/*.trx
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, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging
Could not find any files for ./test-results/*.trx
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/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'
Slow Test: frontend/[chromium] › errorHandling.test.ts#L1
frontend/[chromium] › errorHandling.test.ts took 29.7s
Slow Test: frontend/[firefox] › i18n.test.ts#L1
frontend/[firefox] › i18n.test.ts took 22.0s
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging: backend/FwLite/MiniLcm/InMemoryApi.cs#L177
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging: backend/FwLite/MiniLcm/InMemoryApi.cs#L182
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging: backend/FwLite/MiniLcm/InMemoryApi.cs#L214
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging: backend/FwLite/MiniLcm/InMemoryApi.cs#L233
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging: backend/LfClassicData/LfClassicLexboxApi.cs#L62
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging: backend/LfClassicData/LfClassicLexboxApi.cs#L67
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging: backend/LfClassicData/LfClassicLexboxApi.cs#L201
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging: backend/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
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/FwLite/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L152
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/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L160
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/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L165
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/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L178
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/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L250
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#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/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
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/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L152
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/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L160
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/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L165
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/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L178
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/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L250
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.
🎭 Playwright Run Summary
3 failed [chromium] › emailWorkflow.test.ts:115:1 › register via new-user invitation email ────────────── [firefox] › emailWorkflow.test.ts:28:1 › register, verify, update, verify email address ──────── [firefox] › emailWorkflow.test.ts:115:1 › register via new-user invitation email ─────────────── 4 flaky [chromium] › emailWorkflow.test.ts:28:1 › register, verify, update, verify email address ─────── [chromium] › userPage.test.ts:31:1 › can reset password ──────────────────────────────────────── [firefox] › errorHandling.test.ts:141:1 › page load 403 on home page is redirected to login ──── [firefox] › userPage.test.ts:31:1 › can reset password ───────────────────────────────────────── 55 passed (12.3m)

Artifacts

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