Skip to content

Flaky test - TransportAdapter.cancelRequest/winHttp #5244

@antkmsft

Description

@antkmsft

My thoughts - the test itself is ok, but something fails during the test tear down phase.

Other strange thing, I don't remember this test being flaky before, and also I can't remember us changing anything in that code recently, but I could be wrong.

test 298
        Start 298: azure-core.Test/TransportAdapter.cancelRequest/winHttp

298: Test command: D:\a\_work\1\s\build\sdk\core\azure-core\test\ut\Release\azure-core-test.exe "--gtest_filter=Test/TransportAdapter.cancelRequest/winHttp" "--gtest_also_run_disabled_tests"
298: Working Directory: D:/a/_work/1/s/build/sdk/core/azure-core/test/ut
298: Test timeout computed to be: 10000000
298: Note: Google Test filter = Test/TransportAdapter.cancelRequest/winHttp
298: [==========] Running 1 test from 1 test suite.
298: [----------] Global test environment set-up.
298: [----------] 1 test from Test/TransportAdapter
298: [ RUN      ] Test/TransportAdapter.cancelRequest/winHttp
298: [2024-01-10T04:36:16.5566552Z T: 1e94] INFO  : HTTP Request : GET https://azuresdkforcpp.azurewebsites.net/delay/10
298: user-agent : azsdk-cpp-TransportTest/X.X (Windows Server 2019 Datacenter 6.3 17763 17763.1.amd64fre.rs5_release.180914-1434)
298: x-ms-client-request-id : 30b5e058-bee5-4e19-9057-ef0f687dc18c
298: [2024-01-10T04:36:16.5619668Z T: 2084] INFO  : Status operation: 1(WINHTTP_CALLBACK_STATUS_RESOLVING_NAME )
298: [2024-01-10T04:36:16.5643286Z T: 15d0] INFO  : Status operation: 2(WINHTTP_CALLBACK_STATUS_NAME_RESOLVED )
298: [2024-01-10T04:36:16.5652809Z T: 15d0] INFO  : Status operation: 4(WINHTTP_CALLBACK_STATUS_CONNECTING_TO_SERVER )
298: [2024-01-10T04:36:16.6279777Z T: 15d0] INFO  : Status operation: 8(WINHTTP_CALLBACK_STATUS_CONNECTED_TO_SERVER )
298: [2024-01-10T04:36:16.7604407Z T: 15d0] INFO  : Status operation: 16(WINHTTP_CALLBACK_STATUS_SENDING_REQUEST )
298: [2024-01-10T04:36:16.7605582Z T: 15d0] INFO  : Status operation: 32(WINHTTP_CALLBACK_STATUS_REQUEST_SENT )
298: [2024-01-10T04:36:19.7967801Z T: 1e94] DEBUG : WinHttpRequest::~WinHttpRequest. Closing handle synchronously.
298: [2024-01-10T04:36:19.7970066Z T: 15d0] INFO  : Status operation: 2097152(WINHTTP_CALLBACK_STATUS_REQUEST_ERROR )
298: [2024-01-10T04:36:19.7972295Z T: 15d0] ERROR : Request error.  Error Code: 12017: The operation has been canceled
298: . 5
298: [       OK ] Test/TransportAdapter.cancelRequest/winHttp (3240 ms)
298: [----------] 1 test from Test/TransportAdapter (3240 ms total)
298: 
298: [----------] Global test environment tear-down
298: [==========] 1 test from 1 test suite ran. (3240 ms total)
298: [  PASSED  ] 1 test.
298/495 Test #298: azure-core.Test/TransportAdapter.cancelRequest/winHttp ............................................Exit code 0xc0000409
***Exception:   3.25 sec
test 299

...

99% tests passed, 1 tests failed out of 495

...

The following tests FAILED:
	298 - azure-core.Test/TransportAdapter.cancelRequest/winHttp (Exit code 0xc0000409
)

Metadata

Metadata

Assignees

Labels

Azure.CoreClientThis issue points to a problem in the data-plane of the library.blocking-releaseBlocks releasebugThis issue requires a change to an existing behavior in the product in order to be resolved.test-reliabilityIssue that causes tests to be unreliable

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions