-
Notifications
You must be signed in to change notification settings - Fork 10.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix E2ETest.ServerExecutionTests.CircuitTests.ComponentLifecycleMethodThrowsExceptionTerminatesTheCircuit
#57604
base: main
Are you sure you want to change the base?
Conversation
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! If this is a reliable fix, you could probably unquarantine the tests at the same time (since they were not actually flaky but 100% failing all the time).
I'm not totally sure, but it seems related to the testing environment. The way I was able to repro this was shrinking the browser window vertically. I tried various Chrome versions to see if it that was the cause, but it didn't make a difference. |
Hm, let's wait before merging. Despite this fixing the problem for me locally, it didn't seem to fix the problem in CI... |
Looks like this PR hasn't been active for some time and the codebase could have been changed in the meantime. |
Blazor's error UI was overlaying the button that the test was trying to click. This PR fixes the issue by scrolling the button into view before attempting to click it.
Marks #57551 as
test-fixed
.