Skip to content
publish-package

Removes closure allocation, improves few other scenarios #1332

Sign in to view logs

Removes closure allocation, improves few other scenarios

Removes closure allocation, improves few other scenarios #1332

Triggered via push January 5, 2026 23:51
@soennekersoenneker
pushed 2da4165
main
Status Success
Total duration 34s
Artifacts –

publish-package.yml

on: push
publish-package
31s
publish-package
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
publish-package: test/Soenneker.Utils.MemoryStream.Tests/MemoryStreamUtilTests.cs#L128
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
publish-package: test/Soenneker.Utils.MemoryStream.Tests/MemoryStreamUtilTests.cs#L156
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
publish-package: test/Soenneker.Utils.MemoryStream.Tests/MemoryStreamUtilTests.cs#L91
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
publish-package: test/Soenneker.Utils.MemoryStream.Tests/MemoryStreamUtilTests.cs#L78
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
publish-package: test/Soenneker.Utils.MemoryStream.Tests/MemoryStreamUtilTests.cs#L41
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
publish-package: test/Soenneker.Utils.MemoryStream.Tests/MemoryStreamUtilTests.cs#L50
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
publish-package: test/Soenneker.Utils.MemoryStream.Tests/MemoryStreamUtilTests.cs#L49
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
publish-package: test/Soenneker.Utils.MemoryStream.Tests/MemoryStreamUtilTests.cs#L40
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
publish-package: test/Soenneker.Utils.MemoryStream.Tests/MemoryStreamUtilTests.cs#L32
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
publish-package: test/Soenneker.Utils.MemoryStream.Tests/MemoryStreamUtilTests.cs#L24
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)