Skip to content

Integration Tests Everywhere! #3

Integration Tests Everywhere!

Integration Tests Everywhere! #3

Triggered via pull request November 15, 2025 23:30
Status Failure
Total duration 2m 38s
Artifacts 4

integration-tests.yml

on: pull_request
Matrix: tests
Test Results
21s
Test Results
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 1 warning
Integration Tests (macos-14)
Process completed with exit code 1.
Integration Tests (ubuntu-24.04)
Process completed with exit code 1.
Failed Test: NotificationTests - Notification_is_supported_check: Ubuntu#L28
NotificationTests - Notification_is_supported_check: Expected supported to be True, but found False. - at FluentAssertions.Execution.LateBoundTestFramework.Throw(String message) at FluentAssertions.Execution.DefaultAssertionStrategy.HandleFailure(String message) at FluentAssertions.Execution.AssertionScope.AddPreFormattedFailure(String formattedFailureMessage) at FluentAssertions.Execution.AssertionChain.FailWith(Func`1 getFailureReason) at FluentAssertions.Execution.AssertionChain.FailWith(Func`1 getFailureReason) at FluentAssertions.Execution.AssertionChain.FailWith(String message, Object[] args) at FluentAssertions.Primitives.BooleanAssertions`1.BeTrue(String because, Object[] becauseArgs) at ElectronNET.IntegrationTests.Tests.NotificationTests.Notification_is_supported_check() in /home/runner/work/Electron.NET/Electron.NET/src/ElectronNET.IntegrationTests/Tests/NotificationTests.cs:line 28 --- End of stack trace from previous location ---
Failed Test: NotificationTests - Notification_create_check: Ubuntu#L21
NotificationTests - Notification_create_check: Expected tcs.Task.IsCompletedSuccessfully to be True, but found False. - at FluentAssertions.Execution.LateBoundTestFramework.Throw(String message) at FluentAssertions.Execution.DefaultAssertionStrategy.HandleFailure(String message) at FluentAssertions.Execution.AssertionScope.AddPreFormattedFailure(String formattedFailureMessage) at FluentAssertions.Execution.AssertionChain.FailWith(Func`1 getFailureReason) at FluentAssertions.Execution.AssertionChain.FailWith(Func`1 getFailureReason) at FluentAssertions.Execution.AssertionChain.FailWith(String message, Object[] args) at FluentAssertions.Primitives.BooleanAssertions`1.BeTrue(String because, Object[] becauseArgs) at ElectronNET.IntegrationTests.Tests.NotificationTests.Notification_create_check() in /home/runner/work/Electron.NET/Electron.NET/src/ElectronNET.IntegrationTests/Tests/NotificationTests.cs:line 21 --- End of stack trace from previous location ---
Failed Test: BrowserWindowTests - Represented_filename_and_edited_flags: macOS#L209
BrowserWindowTests - Represented_filename_and_edited_flags: System.TimeoutException : No response after 1000ms trying to retrieve value browserWindow.IsDocumentEditedAsync() - at ElectronNET.IntegrationTests.Tests.BrowserWindowTests.Represented_filename_and_edited_flags() in /Users/runner/work/Electron.NET/Electron.NET/src/ElectronNET.IntegrationTests/Tests/BrowserWindowTests.cs:line 209 --- End of stack trace from previous location ---
Test Results
Github Test Reporter: 3 failed tests found
Failed Test: Notification_is_supported_check: Ubuntu#L28
Notification_is_supported_check: Expected supported to be True, but found False. - at FluentAssertions.Execution.LateBoundTestFramework.Throw(String message) at FluentAssertions.Execution.DefaultAssertionStrategy.HandleFailure(String message) at FluentAssertions.Execution.AssertionScope.AddPreFormattedFailure(String formattedFailureMessage) at FluentAssertions.Execution.AssertionChain.FailWith(Func`1 getFailureReason) at FluentAssertions.Execution.AssertionChain.FailWith(Func`1 getFailureReason) at FluentAssertions.Execution.AssertionChain.FailWith(String message, Object[] args) at FluentAssertions.Primitives.BooleanAssertions`1.BeTrue(String because, Object[] becauseArgs) at ElectronNET.IntegrationTests.Tests.NotificationTests.Notification_is_supported_check() in /home/runner/work/Electron.NET/Electron.NET/src/ElectronNET.IntegrationTests/Tests/NotificationTests.cs:line 28 --- End of stack trace from previous location ---
Failed Test: Notification_create_check: Ubuntu#L21
Notification_create_check: Expected tcs.Task.IsCompletedSuccessfully to be True, but found False. - at FluentAssertions.Execution.LateBoundTestFramework.Throw(String message) at FluentAssertions.Execution.DefaultAssertionStrategy.HandleFailure(String message) at FluentAssertions.Execution.AssertionScope.AddPreFormattedFailure(String formattedFailureMessage) at FluentAssertions.Execution.AssertionChain.FailWith(Func`1 getFailureReason) at FluentAssertions.Execution.AssertionChain.FailWith(Func`1 getFailureReason) at FluentAssertions.Execution.AssertionChain.FailWith(String message, Object[] args) at FluentAssertions.Primitives.BooleanAssertions`1.BeTrue(String because, Object[] becauseArgs) at ElectronNET.IntegrationTests.Tests.NotificationTests.Notification_create_check() in /home/runner/work/Electron.NET/Electron.NET/src/ElectronNET.IntegrationTests/Tests/NotificationTests.cs:line 21 --- End of stack trace from previous location ---
Failed Test: Represented_filename_and_edited_flags: macOS#L209
Represented_filename_and_edited_flags: System.TimeoutException : No response after 1000ms trying to retrieve value browserWindow.IsDocumentEditedAsync() - at ElectronNET.IntegrationTests.Tests.BrowserWindowTests.Represented_filename_and_edited_flags() in /Users/runner/work/Electron.NET/Electron.NET/src/ElectronNET.IntegrationTests/Tests/BrowserWindowTests.cs:line 209 --- 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:037ca1d63f19e84de82c5b3e744421adaf10b3e3b7a6c3fbc59dc36b9ec86121
test-results-macos-14 Expired
21.7 KB
sha256:d280a9434d3e18ca6a1608e3d10233b0dc1d9fc4c3ddcbfe91b94a9512ac2b3b
test-results-ubuntu-24.04 Expired
22.9 KB
sha256:d741688061cee73ff0c4724415d40890c069871cc94251d54d32b488469653f7
test-results-windows-2022 Expired
20.8 KB
sha256:d9981e42de4568645dbd3aba9b6672bf597f3b24410cb2b1ca48eb6e3db1ab75