We were unable to automatically build your code. Please replace the call to the autobuild action with your custom build steps. Encountered a fatal error while running "/opt/hostedtoolcache/CodeQL/2.23.3/x64/codeql/csharp/tools/autobuild.sh". Exit code was 1 and last log line was: Error: Could not auto-detect a suitable build method. See the logs for more details.

'IWaitForContainerOS' does not contain a definition for 'UntilPortIsAvailable' and no accessible extension method 'UntilPortIsAvailable' accepting a first argument of type 'IWaitForContainerOS' could be found (are you missing a using directive or an assembly reference?)

'IWaitForContainerOS' does not contain a definition for 'UntilPortIsAvailable' and no accessible extension method 'UntilPortIsAvailable' accepting a first argument of type 'IWaitForContainerOS' could be found (are you missing a using directive or an assembly reference?)

'IWaitForContainerOS' does not contain a definition for 'UntilPortIsAvailable' and no accessible extension method 'UntilPortIsAvailable' accepting a first argument of type 'IWaitForContainerOS' could be found (are you missing a using directive or an assembly reference?)

'IWaitForContainerOS' does not contain a definition for 'UntilPortIsAvailable' and no accessible extension method 'UntilPortIsAvailable' accepting a first argument of type 'IWaitForContainerOS' could be found (are you missing a using directive or an assembly reference?)

'IWaitForContainerOS' does not contain a definition for 'UntilPortIsAvailable' and no accessible extension method 'UntilPortIsAvailable' accepting a first argument of type 'IWaitForContainerOS' could be found (are you missing a using directive or an assembly reference?)

'IWaitForContainerOS' does not contain a definition for 'UntilPortIsAvailable' and no accessible extension method 'UntilPortIsAvailable' accepting a first argument of type 'IWaitForContainerOS' could be found (are you missing a using directive or an assembly reference?)

Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)

Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)

Public method 'UsesMultipleThreadsWhenConfigured' on test class 'Test' should be marked as a Fact. Reduce the visibility of the method, or add a Fact attribute to the method. (https://xunit.net/xunit.analyzers/rules/xUnit1013)

Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)

Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)

Public method 'UsesMultipleThreadsWhenConfigured' on test class 'Test' should be marked as a Fact. Reduce the visibility of the method, or add a Fact attribute to the method. (https://xunit.net/xunit.analyzers/rules/xUnit1013)

Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)

Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)