fix integration tests depending on the home button. #67
release-pipeline.yaml
on: push
Set Version
0s
Build API
/
publish-api
2m 59s
Build UI
/
publish-ui
2m 3s
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, 103 warnings, and 1 notice
Integration tests (ubuntu-latest, 6) / Playwright tests on ubuntu-latest for Mercurial 6 on staging
Process completed with exit code 2.
|
[chromium] βΊ resetProject.test.ts:20:1 βΊ reset project and upload .zip file:
frontend/tests/resetProject.test.ts#L35
1) [chromium] βΊ resetProject.test.ts:20:1 βΊ reset project and upload .zip file βββββββββββββββββββ
Error: Timed out 5000ms waiting for expect(locator).toBeVisible()
Locator: getByText('Project successfully reset')
Expected: visible
Received: <element(s) not found>
Call log:
- expect.toBeVisible with timeout 5000ms
- waiting for getByText('Project successfully reset')
33 | await resetProjectModel.clickNextStepButton('Reset project');
34 | await resetProjectModel.uploadProjectZipFile('tests/data/test-project-one-commit.zip');
> 35 | await expect(page.getByText('Project successfully reset')).toBeVisible();
| ^
36 | await page.getByRole('button', { name: 'Close' }).click();
37 | await resetProjectModel.assertGone();
38 |
at /home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/resetProject.test.ts:35:62
|
[chromium] βΊ resetProject.test.ts:20:1 βΊ reset project and upload .zip file:
frontend/tests/resetProject.test.ts#L75
1) [chromium] βΊ resetProject.test.ts:20:1 βΊ reset project and upload .zip file βββββββββββββββββββ
Retry #1 βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
Error: Timed out 5000ms waiting for expect(locator).toBeVisible()
Locator: getByText('Project successfully reset')
Expected: visible
Received: <element(s) not found>
Call log:
- expect.toBeVisible with timeout 5000ms
- waiting for getByText('Project successfully reset')
73 | await resetProjectModel.clickNextStepButton('Reset project');
74 | await resetProjectModel.uploadProjectZipFile(join(tempDir, 'reset-project-test-step-1.zip'));
> 75 | await expect(page.getByText('Project successfully reset')).toBeVisible();
| ^
76 | await page.getByRole('button', { name: 'Close' }).click();
77 | await resetProjectModel.assertGone();
78 |
at /home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/resetProject.test.ts:75:62
|
[firefox] βΊ emailWorkflow.test.ts:78:1 βΊ forgot password:
frontend/tests/pages/mailPages.ts#L38
2) [firefox] βΊ 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
|
[firefox] βΊ emailWorkflow.test.ts:78:1 βΊ forgot password:
frontend/tests/pages/mailPages.ts#L38
2) [firefox] βΊ 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
|
[firefox] βΊ emailWorkflow.test.ts:115:1 βΊ register via new-user invitation email:
frontend/tests/fixtures.ts#L40
3) [firefox] βΊ emailWorkflow.test.ts:115:1 βΊ register via new-user invitation email ββββββββββββββ
Error: Unexpected response status: 502. (Request URL: https://staging.languagedepot.org/api/graphql. Traceparent: 00-cd524d7696dcbf88dc51a75818c528db-efa58f68b2fa3def-01.)
expect(received).toBeLessThan(expected)
Expected: < 500
Received: 502
at fixtures.ts:40
38 | const url = response.request().url();
39 | const unexpectedResponseMessage = `Unexpected response status: ${status}. (Request URL: ${url}. Traceparent: ${traceparent}.)`;
> 40 | expect.soft(response.status(), unexpectedResponseMessage).toBeLessThan(500);
| ^
41 | if (response.request().isNavigationRequest()) {
42 | expect.soft(response.status(), unexpectedResponseMessage).toBeLessThan(400);
43 | }
at BrowserContext.<anonymous> (/home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/fixtures.ts:40:63)
|
[firefox] βΊ emailWorkflow.test.ts:115:1 βΊ register via new-user invitation email:
frontend/tests/fixtures.ts#L40
3) [firefox] βΊ emailWorkflow.test.ts:115:1 βΊ register via new-user invitation email ββββββββββββββ
Error: Unexpected response status: 503. (Request URL: https://staging.languagedepot.org/v1/traces. Traceparent: undefined.)
expect(received).toBeLessThan(expected)
Expected: < 500
Received: 503
at fixtures.ts:40
38 | const url = response.request().url();
39 | const unexpectedResponseMessage = `Unexpected response status: ${status}. (Request URL: ${url}. Traceparent: ${traceparent}.)`;
> 40 | expect.soft(response.status(), unexpectedResponseMessage).toBeLessThan(500);
| ^
41 | if (response.request().isNavigationRequest()) {
42 | expect.soft(response.status(), unexpectedResponseMessage).toBeLessThan(400);
43 | }
at BrowserContext.<anonymous> (/home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/fixtures.ts:40:63)
|
[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 ended.
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/pages/mailPages.ts#L38
3) [firefox] βΊ emailWorkflow.test.ts:115:1 βΊ register via new-user invitation email ββββββββββββββ
Retry #1 βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
Error: Failed to find email: Project invitation: (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:134:37
|
[firefox] βΊ errorHandling.test.ts:141:1 βΊ page load 403 on home page is redirected to login:
frontend/tests/pages/mailPages.ts#L38
4) [firefox] βΊ errorHandling.test.ts:141:1 βΊ page load 403 on home page is redirected to login βββ
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
|
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, 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/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#L167
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#L175
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#L255
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/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/FwDataMiniLcmBridge/Api/UpdateProxy/UpdateSenseProxy.cs#L89
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/LexData/SeedingData.cs#L18
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
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
'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 'lexAuthService' is unread.
|
Build API / publish-api
Parameter 'lexBoxDbContext' 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
Parameter 'hgService' is unread.
|
Build API / publish-api
No files were found with the provided path: ./test-results. No artifacts will be uploaded.
|
Slow Test:
frontend/[chromium] βΊ emailWorkflow.test.ts#L1
frontend/[chromium] βΊ emailWorkflow.test.ts took 35.8s
|
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/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#L167
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#L175
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#L255
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/LcmUtils/LcmThreadedProgress.cs#L10
The event 'LcmThreadedProgress.Canceling' is never used
|
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging:
backend/FwDataMiniLcmBridge/Api/UpdateProxy/UpdateSenseProxy.cs#L89
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)
|
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging:
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)
|
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/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L167
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#L175
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#L255
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/LcmUtils/LcmThreadedProgress.cs#L10
The event 'LcmThreadedProgress.Canceling' is never used
|
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging:
backend/FwDataMiniLcmBridge/Api/UpdateProxy/UpdateSenseProxy.cs#L89
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)
|
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging:
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)
|
Integration tests (ubuntu-latest, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 on staging:
backend/LfClassicData/LfClassicLexboxApi.cs#L191
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, 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/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/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#L167
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#L175
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#L255
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/LcmUtils/LcmThreadedProgress.cs#L10
The event 'LcmThreadedProgress.Canceling' is never used
|
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging:
backend/FwDataMiniLcmBridge/Api/UpdateProxy/UpdateSenseProxy.cs#L89
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)
|
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging:
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)
|
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging:
backend/LfClassicData/LfClassicLexboxApi.cs#L191
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
|
|
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging:
backend/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L167
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#L175
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#L255
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/LcmUtils/LcmThreadedProgress.cs#L10
The event 'LcmThreadedProgress.Canceling' is never used
|
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging:
backend/FwDataMiniLcmBridge/Api/UpdateProxy/UpdateSenseProxy.cs#L89
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)
|
Integration tests (ubuntu-latest, 3) / Dotnet tests on ubuntu-latest for Mercurial 3 on staging:
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)
|
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:
backend/LcmCrdt/LcmCrdtKernel.cs#L4
The using directive for 'Crdt' appeared previously in this namespace
|
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/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#L167
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#L175
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#L255
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/LcmUtils/LcmThreadedProgress.cs#L10
The event 'LcmThreadedProgress.Canceling' is never used
|
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging:
backend/FwDataMiniLcmBridge/Api/UpdateProxy/UpdateSenseProxy.cs#L89
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)
|
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging:
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)
|
|
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#L191
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#L167
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#L175
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#L255
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/LcmUtils/LcmThreadedProgress.cs#L10
The event 'LcmThreadedProgress.Canceling' is never used
|
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging:
backend/FwDataMiniLcmBridge/Api/UpdateProxy/UpdateSenseProxy.cs#L89
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)
|
Integration tests (windows-latest, 3) / Dotnet tests on windows-latest for Mercurial 3 on staging:
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)
|
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, 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/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/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#L167
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#L175
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#L255
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/LcmUtils/LcmThreadedProgress.cs#L10
The event 'LcmThreadedProgress.Canceling' is never used
|
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging:
backend/FwDataMiniLcmBridge/Api/UpdateProxy/UpdateSenseProxy.cs#L89
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)
|
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging:
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)
|
|
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/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L167
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#L175
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#L255
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/LcmUtils/LcmThreadedProgress.cs#L10
The event 'LcmThreadedProgress.Canceling' is never used
|
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging:
backend/FwDataMiniLcmBridge/Api/UpdateProxy/UpdateSenseProxy.cs#L89
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)
|
Integration tests (windows-latest, 6) / Dotnet tests on windows-latest for Mercurial 6 on staging:
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)
|
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:
backend/LfClassicData/LfClassicLexboxApi.cs#L191
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
6 failed
[chromium] βΊ resetProject.test.ts:20:1 βΊ reset project and upload .zip file ββββββββββββββββββββ
[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 βββββββββββββββββββββ
[firefox] βΊ userPage.test.ts:31:1 βΊ can reset password βββββββββββββββββββββββββββββββββββββββββ
2 flaky
[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 ββββββββββββββββββββββββββββββββββββββββ
54 passed (9.9m)
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
playwright-traces-ubuntu-latest-hg-6
Expired
|
214 MB |
|