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

follow-up(#7077): adjust flaky-test-detection cutoff date for tokio-epoll-uring #7090

Merged
merged 2 commits into from Mar 11, 2024

Conversation

problame
Copy link
Contributor

No description provided.

@problame problame requested a review from bayandin March 11, 2024 14:56
@problame problame marked this pull request as ready for review March 11, 2024 14:56
scripts/flaky_tests.py Outdated Show resolved Hide resolved
Co-authored-by: Alexander Bayandin <alexander@neon.tech>
@problame problame enabled auto-merge (squash) March 11, 2024 15:55
@problame problame merged commit 17a3c90 into main Mar 11, 2024
50 checks passed
@problame problame deleted the problame/linux-default-tokio-epoll-uring-followup branch March 11, 2024 16:36
Copy link

2496 tests run: 2373 passed, 0 failed, 123 skipped (full report)


Flaky tests (1)

Postgres 16

  • test_compute_pageserver_connection_stress: release

Code coverage* (full report)

  • functions: 28.8% (7032 of 24443 functions)
  • lines: 47.6% (43452 of 91297 lines)

* collected from Rust tests only


The comment gets automatically updated with the latest test results
b2854fc at 2024-03-11T16:48:00.530Z :recycle:

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.

None yet

2 participants