ElectronNET.API: Add platform support attributes #8
integration-tests.yml
on: pull_request
Matrix: tests
Test Results
25s
Annotations
4 errors and 1 warning
|
Integration Tests (macos-14)
Process completed with exit code 1.
|
|
Failed Test: BrowserWindowTests - Progress_bar_and_always_on_top_toggle:
macOS#L172
BrowserWindowTests - Progress_bar_and_always_on_top_toggle: Expected (win.IsAlwaysOnTopAsync()) to be False, but found True. - at FluentAssertions.Execution.LateBoundTestFramework.Throw(String message)
at FluentAssertions.Execution.DefaultAssertionStrategy.HandleFailure(String message)
at FluentAssertions.Execution.AssertionChain.FailWith(Func`1 getFailureReason)
at FluentAssertions.Primitives.BooleanAssertions`1.BeFalse(String because, Object[] becauseArgs)
at ElectronNET.IntegrationTests.Tests.BrowserWindowTests.Progress_bar_and_always_on_top_toggle() in /Users/runner/work/Electron.NET/Electron.NET/src/ElectronNET.IntegrationTests/Tests/BrowserWindowTests.cs:line 172
--- End of stack trace from previous location ---
|
|
Test Results
Github Test Reporter: 1 failed tests found
|
|
Failed Test: Progress_bar_and_always_on_top_toggle:
macOS#L172
Progress_bar_and_always_on_top_toggle: Expected (win.IsAlwaysOnTopAsync()) to be False, but found True. - at FluentAssertions.Execution.LateBoundTestFramework.Throw(String message)
at FluentAssertions.Execution.DefaultAssertionStrategy.HandleFailure(String message)
at FluentAssertions.Execution.AssertionChain.FailWith(Func`1 getFailureReason)
at FluentAssertions.Primitives.BooleanAssertions`1.BeFalse(String because, Object[] becauseArgs)
at ElectronNET.IntegrationTests.Tests.BrowserWindowTests.Progress_bar_and_always_on_top_toggle() in /Users/runner/work/Electron.NET/Electron.NET/src/ElectronNET.IntegrationTests/Tests/BrowserWindowTests.cs:line 172
--- End of stack trace from previous location ---
|
|
Test Results
Resource not accessible by integration - https://docs.github.com/rest/issues/comments#create-an-issue-comment
Unable to post PR comment - this is likely a permissions issue.
Required permission: "pull-requests: write" needs to be set in your workflow permissions.
Add this to your workflow file:
jobs:
build:
runs-on: ubuntu-latest
permissions:
pull-requests: write
See documentation: https://docs.github.com/en/actions/security-for-github-actions/security-guides/automatic-token-authentication#modifying-the-permissions-for-the-github_token
For forked PRs, you should use the pull_request_target event instead of pull_request.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
ctrf-report
|
33.5 KB |
sha256:808b19e83899824882856ab7b2255c4ee09f6bcbbd10618514cf9bd128f1f89b
|
|
|
test-results-macos-14
Expired
|
21.8 KB |
sha256:0f322161dec4589723f4a86420fcc356507e4b7e61ab687282b6267130e7ea63
|
|
|
test-results-ubuntu-24.04
Expired
|
21.9 KB |
sha256:53e30abfa280d1fab0f7181715e1827507f3558110bfe06219e0db34dcbfba61
|
|
|
test-results-windows-2022
Expired
|
20.6 KB |
sha256:435b3d8a5cc74109127d90035af73a725cd6f4b2936e9b057814c33abe108fa7
|
|