[Failing test] QuicCryptoClientStreamTest.ConnectedAfterTlsHandshake on Android CFI |
||||
Issue descriptionBot : https://ci.chromium.org/buildbot/chromium.memory/Android%20CFI/?limit=200 Regression range : https://chromium.googlesource.com/chromium/src/+log/673c2965225fa332750026da6686cc3a0453d157..5e64c59cc7704c25c81311b5ec2c78ddb5ca9af9?pretty=fuller&n=10000 No QUIC changes in that range, seems likely related to https://chromium-review.googlesource.com/1069537 @kbr PTaL (I did not revert since your change was on Infra side but please do if that's the fastest course of action)
,
May 24 2018
Adding rch@ who recently moved the tests to where they are now and might be more familiar with failure causes for these tests. Ftr, the crash log is usually along the lines of [ RUN ] QuicCryptoClientStreamTest.ConnectedAfterTlsHandshake ../../net/third_party/quic/test_tools/crypto_test_utils.cc:532: Failure Expected: (client_conn->encrypted_packets_.size()) > (client_i), actual: 1 vs 1 Stack trace: [ CRASHED ] Searching for native crashes in: /b/swarming/w/ita0oUwQ/tmp95kwje Unknown Android release, consider passing --packed-lib. Reading Android symbols from: /b/swarming/w/ir Searching for Chrome symbols from within: /b/swarming/w/ir/out/Release/lib.unstripped:/b/swarming/w/ir/out/Release
,
May 25 2018
seems to have gone green in https://ci.chromium.org/buildbot/chromium.memory/Android%20CFI/1344 maybe fixed by the roll in https://chromium-review.googlesource.com/1070648
,
May 26 2018
Yes, it looks like that roll fixed it. I don't maintain this bot, was only helping to get one of the test suites (content_browsertests) running properly again. Closing as WontFix since it was fixed by https://chromium-review.googlesource.com/1070648 . |
||||
►
Sign in to add a comment |
||||
Comment 1 by gab@chromium.org
, May 23 2018