Closed andybalaam closed 10 months ago
Hmm... is there not a way of debugging the focus issue locally? (though I guess there should not be, as we could just use it instead of their service)
(though I guess there should not be, as we could just use it instead of their service)
Sure, you can run the cypress tests locally, the same issue should be present there, though make sure to not have your cursor over the cypress window to avoid impacting the focus
Hmm... is there not a way of debugging the focus issue locally? (though I guess there should not be, as we could just use it instead of their service)
Yeah, we definitely want to fix these issues (and would appreciate help!) but at the moment I am reviewing and closing ~10-20 failures per day, meaning that I won't notice real errors, so disabling them is the less-bad option than just leaving them.
Yeah, we definitely want to fix these issues (and would appreciate help!) but at the moment I am reviewing and closing ~10-20 failures per day, meaning that I won't notice real errors, so disabling them is the less-bad option than just leaving them.
Ahh, my intention was not to ask you to debug the issues, but to ask how I can debug to stop creating flaky percy tests before creating PRs as most of them listed above were based on recent PRs I've pushed...
Sure, you can run the cypress tests locally, the same issue should be present there, though make sure to not have your cursor over the cypress window to avoid impacting the focus
Yes, it is surely possible to run cypress tests locally (I have tried to minimize risk of flaky tests by running them locally before creating a PR), but I could not manage to spot the flakiness :frowning: Maybe something happens in milliseconds.
Ahh, my intention was not to ask you to debug the issues, but to ask how I can debug to stop creating flaky percy tests before creating PRs as most of them listed above were based on recent PRs I've pushed...
Ah, that is great, thank you for trying! These failures seem really hard to debug, but we'll get there. Please don't give up creating the tests - they will be really helpful when we have made them work properly :-)
Sure, you can run the cypress tests locally, the same issue should be present there, though make sure to not have your cursor over the cypress window to avoid impacting the focus
Yes, it is surely possible to run cypress tests locally (I have tried to minimize risk of flaky tests by running them locally before creating a PR), but I could not manage to spot the flakiness frowning Maybe something happens in milliseconds.
I have tried similarly with the variable-height dropdown and I can't see anything locally :-(
I suspect that the flakiness of a reply / ReplyChain
is caused by the fact that the color of vertical strokes changes randomly per each run (the test user is created randomly -> the color of the user name disambiguatedProfile
changes randomly too -> the color of the strokes changes too as it depends on the user name color).
The same issue has been experienced for BaseAvatar
too (please see: _BaseAvatar.pcss
).
I am going to create a PR to (hopefully) address this.
Created the PR to apply the same color to the left borders of ReplyChain
consistently: https://github.com/matrix-org/matrix-react-sdk/pull/10450
I haven't seen this for a while, so assuming it's fixed. Will re-open if not.
Nope, I forgot that I had disabled the related test.
Disabling:
because they are flaky due to variable keyboard focus.
We are not using Percy any more. Closing this.
Test failure examples:
These all seem to fail because the (keyboard?) focus varies between test runs.