cfriedt commented on pull request #2007: URL: https://github.com/apache/thrift/pull/2007#issuecomment-911474376
> Ok @cfried, I'm sorry but there is indeed a problem: With your changes, there are consistent crashes on all Windows builds (MSVC and MINGW) in `processor_test`, see https://ci.appveyor.com/project/ApacheSoftwareFoundation/thrift/builds/40571399. With another very recent build from yesterday, we do not get these, see https://ci.appveyor.com/project/ApacheSoftwareFoundation/thrift/builds/40603625. Odd - yeah, the logs show this: ``` [00:15:37] 397: Test command: C:\projects\build\MSVC2017\x64\bin\Release\processor_test.exe [00:15:37] 397: Test timeout computed to be: 300 [00:15:39] 397: Thrift: Mon Aug 30 10:33:14 2021 TNonblockingServer: Serving with 1 io threads. [00:15:39] 397: Thrift: Mon Aug 30 10:33:14 2021 TNonblockingServer: using libevent 2.1.8-stable method win32 [00:15:39] 397: Thrift: Mon Aug 30 10:33:14 2021 TNonblocking: IO thread #0 registered for listen. [00:15:39] 397: Thrift: Mon Aug 30 10:33:14 2021 TNonblocking: IO thread #0 registered for notify. [00:15:39] 397: Thrift: Mon Aug 30 10:33:14 2021 TNonblockingServer: IO thread #0 entering loop... [00:17:43] 397: Thrift: Mon Aug 30 10:35:18 2021 TNonblockingServer: caught bad_alloc exception. [00:17:44] 397: Running 64 test cases... [00:17:46] 397/416 Test #397: processor_test ...................***Failed 128.95 sec ``` I'm not sure where the bad_alloc exception would come from, but I'll look into it if it does not pass after rebasing. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
