Skip to content

Conversation

@drdaz
Copy link
Member

@drdaz drdaz commented Dec 10, 2021

New Pull Request Checklist

Issue Description

We have some generalised flakiness in our tests. This update to xctoolchain should help us to spot and debug flaky tests.

@parse-github-assistant
Copy link

parse-github-assistant bot commented Dec 10, 2021

Thanks for opening this pull request!

  • ❌ Please edit your post and use the provided template when creating a new pull request. This helps everyone to understand your post better and asks for essential information to quicker review the pull request.

@drdaz drdaz changed the title Adds retries for flaky tests enhancement: retries for flaky tests Dec 10, 2021
@drdaz drdaz changed the title enhancement: retries for flaky tests test: retries for flaky tests Dec 10, 2021
@drdaz drdaz requested review from a team December 10, 2021 17:49
@cbaker6
Copy link
Contributor

cbaker6 commented Dec 10, 2021

@drdaz I recommend updating the CI to Xcode 13.2 as I think it may provide more details about the tests.

@drdaz
Copy link
Member Author

drdaz commented Dec 10, 2021

The change also seems to have made no difference here. Hmm...

@drdaz drdaz removed request for a team December 10, 2021 18:00
@drdaz
Copy link
Member Author

drdaz commented Dec 15, 2021

After some poking around, I've come to the conclusion that the retry changes do work here. They just don't help with all of our flaky tests. There are some with occasional logical failures; those will probably work as documented in this test log with a test that just executes XCTFail - there are 10 sets of output showing the failure.

The ones that crash (and these are the bulk of our problem) don't get retried, as can be seen in the current iOS build.

It's not quite the result we could have hoped for, but I definitely think it's worth including.

@mtrezza
Copy link
Member

mtrezza commented Jul 27, 2022

What should we do with this PR? The only flakiness I observed recently was in the macos tests

@mtrezza
Copy link
Member

mtrezza commented Jan 30, 2023

@drdaz Would you like to resolve the conflicts so we can see whether it works? We've had several changes on the main branch and a flaky test left in macOS, so maybe the issue can be solved with this.

@dplewis
Copy link
Member

dplewis commented Mar 7, 2023

@mtrezza I have also ran into this issue with timeout failure.

Screen Shot 2023-03-07 at 12 12 26 PM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants