skip CanUseBearerAuth since it's not currently working since we enabl… #72
release-pipeline.yaml
on: push
Set Version
0s
Build API
/
publish-api
3m 29s
Build UI
/
publish-ui
2m 17s
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
3s
Deployment protection rules
Reviewers, timers, and other rules protecting deployments in this run
Event | Environments |
---|---|
hahn-kev
approved
|
production |
Annotations
15 errors, 104 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] › 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:63:31
|
[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:63:31
|
[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.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
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.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] › adminPage.test.ts:6:1 › can navigate to project page:
frontend/tests/pages/basePage.ts#L58
4) [firefox] › adminPage.test.ts:6:1 › can navigate to project page ──────────────────────────────
Error: Timed out 5000ms waiting for expect(locator).toBeVisible()
Locator: locator('.breadcrumbs :text(\'Sena 3\')')
Expected: visible
Received: <element(s) not found>
Call log:
- expect.toBeVisible with timeout 5000ms
- waiting for locator('.breadcrumbs :text(\'Sena 3\')')
at pages/basePage.ts:58
56 | }
57 | await BasePage.waitForHydration(this.page); // wait for, e.g., onclick handlers to be attached
> 58 | await Promise.all(this.locators.map(l => expect(l).toBeVisible()));
| ^
59 | return this;
60 | }
61 |
at map (/home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/pages/basePage.ts:58:56)
at ProjectPage.waitFor (/home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/pages/basePage.ts:58:37)
at AdminDashboardPage.openProject (/home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/pages/adminDashboardPage.ts:14:12)
at /home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/adminPage.test.ts:11:3
|
[firefox] › adminPage.test.ts:6:1 › can navigate to project page:
frontend/tests/pages/basePage.ts#L53
4) [firefox] › adminPage.test.ts:6:1 › can navigate to project page ──────────────────────────────
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timed out 10000ms waiting for expect(locator).toHaveURL(expected)
Locator: locator(':root')
Expected pattern: /\/admin($|\?|#)/
Received string: "https://staging.languagedepot.org/login"
Call log:
- expect.toHaveURL with timeout 10000ms
- waiting for locator(':root')
- locator resolved to <html lang="en">…</html>
- unexpected value "https://staging.languagedepot.org/login"
- locator resolved to <html lang="en">…</html>
- unexpected value "https://staging.languagedepot.org/login"
- locator resolved to <html lang="en">…</html>
- unexpected value "https://staging.languagedepot.org/login"
- locator resolved to <html lang="en">…</html>
- unexpected value "https://staging.languagedepot.org/login"
- locator resolved to <html lang="en">…</html>
- unexpected value "https://staging.languagedepot.org/login"
- locator resolved to <html lang="en">…</html>
- unexpected value "https://staging.languagedepot.org/login"
- locator resolved to <html lang="en">…</html>
- unexpected value "https://staging.languagedepot.org/login"
- locator resolved to <html lang="en">…</html>
- unexpected value "https://staging.languagedepot.org/login"
- locator resolved to <html lang="en">…</html>
- unexpected value "https://staging.languagedepot.org/login"
- locator resolved to <html lang="en">…</html>
- unexpected value "https://staging.languagedepot.org/login"
- locator resolved to <html lang="en">…</html>
- unexpected value "https://staging.languagedepot.org/login"
- locator resolved to <html lang="en">…</html>
- unexpected value "https://staging.languagedepot.org/login"
- locator resolved to <html lang="en">…</html>
- unexpected value "https://staging.languagedepot.org/login"
- locator resolved to <html lang="en">…</html>
- unexpected value "https://staging.languagedepot.org/login"
at pages/basePage.ts:53
51 | } else {
52 | // first use expect() so we get a good error message
> 53 | await expect(this.page).toHaveURL(this.urlPattern, {timeout: 10_000});
| ^
54 | // still wait to ensure we reach the state we expect
55 | await this.page.waitForURL(this.urlPattern, {waitUntil: 'load'});
56 | }
at AdminDashboardPage.waitFor (/home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/pages/basePage.ts:53:31)
at /home/runner/work/languageforge-lexbox/languageforge-lexbox/frontend/tests/adminPage.test.ts:10:56
|
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, 6) / Dotnet tests on ubuntu-latest for Mercurial 6 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.
|
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/LexData/SeedingData.cs#L18
Parameter 'logger' is unread.
|
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/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 'lexAuthService' is unread.
|
Slow Test:
frontend/[firefox] › errorHandling.test.ts#L1
frontend/[firefox] › errorHandling.test.ts took 1.2m
|
Slow Test:
frontend/[chromium] › errorHandling.test.ts#L1
frontend/[chromium] › errorHandling.test.ts took 29.8s
|
Slow Test:
frontend/[chromium] › userPage.test.ts#L1
frontend/[chromium] › userPage.test.ts took 17.4s
|
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/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#L360
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, 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#L360
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 (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#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/Services/UserService.cs#L10
Parameter 'lexAuthService' is unread.
|
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#L360
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, 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/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#L360
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
6 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 ──────────────
[firefox] › adminPage.test.ts:6:1 › can navigate to project page ───────────────────────────────
[firefox] › emailWorkflow.test.ts:28:1 › register, verify, update, verify email address ────────
[firefox] › emailWorkflow.test.ts:115:1 › register via new-user invitation email ───────────────
2 flaky
[firefox] › userPage.test.ts:11:1 › can update account info ────────────────────────────────────
[firefox] › userPage.test.ts:31:1 › can reset password ─────────────────────────────────────────
54 passed (13.1m)
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
dotnet-unit-test-results
Expired
|
2.43 KB |
|
playwright-traces-ubuntu-latest-hg-6
Expired
|
381 MB |
|