New console log warnings and suggestions on flaky tests?

[nsoojin]

�Hey there,

I started seeing new type of warning logs as I generate touch events. However it doesn't seem to affect the functionality. Do you know why this started happening?

2022-07-22 14:38:11.471364-0400 IntegrationTestHost[36563:3464107] [EventDispatcher] Found no UIEvent for backing event of type: 1; contextId: 0x9DE5CC17; Event will not be dispatched
2022-07-22 14:38:11.473324-0400 IntegrationTestHost[36563:3464107] [EventDispatcher] Found no UIEvent for backing event of type: 1; contextId: 0x9DE5CC17; Event will not be dispatched
2022-07-22 14:38:11.491951-0400 IntegrationTestHost[36563:3464107] [EventDispatcher] Found no UIEvent for backing event of type: 1; contextId: 0x9DE5CC17; Event will not be dispatched

Another question I have is how are you guys handling the flakiness for Hammer in testing. Although not very often, my tests which rely on using Hammer shows flakiness in CI build machines. Do you encounter similar problems? Do you have any tips on how to mitigate it?

Thanks in advance @gabriellanata

[gabriellanata]

Yeah we're also seeing those warnings. I searched around a bit to see if anyone had seen something like that but couldn't fine anything. Deeper research would probably require some disassembling which I don't have time for now. They don't seem to affect functionality as you said, so maybe wee can ignore them for now.

Regarding flakiness, we haven't experienced many issues. In most cases they've been related to the specific view being tested and we can improve the test itself to make it more resilient. But honestly, from what I've seen, you're probably doing more complex tests than we are 😅

[nsoojin]

Thanks for your input 👍