Skip to content
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

Disable frequently flaky GracefulConnectionClosureHandlingTest(s) #1840

Merged
merged 1 commit into from
Sep 22, 2021

Conversation

idelpivnitskiy
Copy link
Member

Motivation:

These tests are known to be flaky [1]. The cause is identified and the
work is in progress. To improve productivity for other work, let's
disable these tests temporarily until the fix is available.

  1. FlakyTest: GracefulConnectionClosureHandlingTest #1507

Modifications:

  • Disable frequently failing use-case number 5;

Result:

No need to re-run PRB for other PRs multiple times.

Motivation:

These tests are known to be flaky [1]. The cause is identified and the
work is in progress. To improve productivity for other work, let's
disable these tests temporarily until the fix is available.

1. apple#1507

Modifications:

- Disable frequently failing use-case number 5;

Result:

No need to re-run PRB for other PRs multiple times.
@idelpivnitskiy idelpivnitskiy merged commit b8a03c9 into apple:main Sep 22, 2021
@idelpivnitskiy idelpivnitskiy deleted the disable-flaky-tests branch September 22, 2021 22:26
idelpivnitskiy added a commit that referenced this pull request Sep 24, 2021
…1840)

Motivation:

These tests are known to be flaky [1]. The cause is identified and the
work is in progress. To improve productivity for other work, let's
disable these tests temporarily until the fix is available.

1. #1507

Modifications:

- Disable frequently failing use-case number 5;

Result:

No need to re-run PRB for other PRs multiple times.
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.

2 participants