Uh oh!
There was an error while loading. Please reload this page.
Fix for failing WebSocket deflate test on ARM - #52052
Conversation
ghost
commented
Apr 29, 2021
Tagging subscribers to this area: @dotnet/ncl |
CarnaViire
commented
Apr 29, 2021
FYI: CI failures are ongoing infra issue. I will rerun checks after it's fixed |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
danmoseley
commented
Apr 30, 2021
I don't think this should say "Fixes #52031" because we need that issue to remain open to fix the product bug, presumably |
danmoseley
commented
May 7, 2021
Let's close this until we know the naswer. |
CarnaViire
commented
May 11, 2021
As per investigation in #52031 (comment) the fix is working. |
… performance of test on ARM.
45b7656 to
1e10516Comparezlatanov
commented
May 11, 2021
The failing test for websockets indicate that embedded resources haven't been loaded on Android. Is this considered bug somewhere, or if it's common enough, we can remove the message check, and only assert the exception type? |
CarnaViire
commented
May 11, 2021
As I understand, we can ignore that for now. Android test failures are treated as a separate effort. In fact, Android tests are part of separate |
danmoseley
commented
May 11, 2021
@steveisok for the Android issue as I've seen it also. |
I would prefer the failing tests for Android have an ActiveIssue attribute associated to them for now. |
CarnaViire
commented
May 11, 2021
Timings from CI for 15 bits: |
As per #52052 (comment), putting the failing tests under ActiveIssue. Tracking issue: #52645
Fixes#52031