Skip to content
CodeQL

CodeQL #416

Sign in to view logs

CodeQL

CodeQL #416

Triggered via schedule April 21, 2025 08:32
@dnperforsdnperfors
⁠ 951eea1
master
Status Success
Total duration 2m 9s
Artifacts –

codeql.yml

on: schedule
Analyze
2m 5s
Analyze
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
Analyze: test/TestableHttpClient.IntegrationTests/CustomizeJsonSerialization.cs#L42
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)
Analyze: test/TestableHttpClient.IntegrationTests/CustomizeJsonSerialization.cs#L30
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)
Analyze: test/TestableHttpClient.IntegrationTests/CustomizeJsonSerialization.cs#L17
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)
Analyze: test/TestableHttpClient.IntegrationTests/CustomizeJsonSerialization.cs#L42
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)
Analyze: test/TestableHttpClient.IntegrationTests/CustomizeJsonSerialization.cs#L30
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)
Analyze: test/TestableHttpClient.IntegrationTests/CustomizeJsonSerialization.cs#L17
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)