-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Keyboard test fixes v2 #14397
Keyboard test fixes v2 #14397
Conversation
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
3216fce
to
e67106d
Compare
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
{ | ||
// Because we retry on CI we don't want to delete the previous failures | ||
// We want to publish those files for reference | ||
DeleteFiles(Directory(TEST_RESULTS).Path.Combine("*.*").FullPath); |
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.
Is this ok @rmarinho? Will there be results left over from other CI runs that we need to clear out?
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.
Hum, the macos images are not clear, so in a next test run there could be files there?
I wonder if we just need a step to clear this on the yaml timeline when the pipeline starts
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
16cc14d
to
99c1055
Compare
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.
am seeing intermittent failures locally with the Modal keyboard and Adjust/Pan keyboard test :(
but otherwise, changes here LGTM!
Description of Change
#14388 was merged a bit early. I should have left it as draft, we were still seeing occasional failures.