Skip to content

Final NUnit fixups #4103

Final NUnit fixups

Final NUnit fixups #4103

Triggered via push November 30, 2023 22:32
Status Failure
Total duration 26m 41s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

build.yml

on: push
Build, test, package and sign release
26m 29s
Build, test, package and sign release
Fit to window
Zoom out
Zoom in

Annotations

1 error and 6 warnings
Build, test, package and sign release
Process completed with exit code 1.
Build, test, package and sign release: Rdmp.Core.Tests/CommandExecution/CommandInvokerTests.cs#L21
'TimeoutAttribute' is obsolete: '.NET No longer supports aborting threads as it is not a safe thing to do. Update your tests to use CancelAfterAttribute instead'
Build, test, package and sign release: Rdmp.Core.Tests/CommandExecution/CommandInvokerTests.cs#L31
'TimeoutAttribute' is obsolete: '.NET No longer supports aborting threads as it is not a safe thing to do. Update your tests to use CancelAfterAttribute instead'
Build, test, package and sign release: Rdmp.Core.Tests/CommandExecution/CommandInvokerTests.cs#L44
'TimeoutAttribute' is obsolete: '.NET No longer supports aborting threads as it is not a safe thing to do. Update your tests to use CancelAfterAttribute instead'
Build, test, package and sign release: Rdmp.Core.Tests/CommandExecution/CommandInvokerTests.cs#L21
'TimeoutAttribute' is obsolete: '.NET No longer supports aborting threads as it is not a safe thing to do. Update your tests to use CancelAfterAttribute instead'
Build, test, package and sign release: Rdmp.Core.Tests/CommandExecution/CommandInvokerTests.cs#L31
'TimeoutAttribute' is obsolete: '.NET No longer supports aborting threads as it is not a safe thing to do. Update your tests to use CancelAfterAttribute instead'
Build, test, package and sign release: Rdmp.Core.Tests/CommandExecution/CommandInvokerTests.cs#L44
'TimeoutAttribute' is obsolete: '.NET No longer supports aborting threads as it is not a safe thing to do. Update your tests to use CancelAfterAttribute instead'