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.

Sign up for GitHub

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

Jump to bottom

use CI to get some exposure to tokio-epoll-uring #6508

Closed
Tracked by #4744
problame opened this issue Jan 29, 2024 · 2 comments
Closed
Tracked by #4744

use CI to get some exposure to tokio-epoll-uring #6508

problame opened this issue Jan 29, 2024 · 2 comments
Assignees
@problame

Comments

@problame
Copy link
Contributor

  • merge integration PR without the CI changes (i.e., default off, code not tested at runtime)
  • after this week's release, for 48h, switch tests to use it)
  • switch tests back so next release gets
  • fix issues that arose from running it for these 48h
  • repeat until no more issues
  • switch staging over & observe impact on benchmarks
@problame problame self-assigned this Jan 29, 2024
@problame problame mentioned this issue Jan 29, 2024
Closed
@problame problame changed the title drive exposure to tokio-epoll-uring use CI to get some exposure to tokio-epoll-uring Jan 29, 2024
@jcsp
Copy link
Contributor

jcsp commented Jan 29, 2024

Already happened, ticket is just open for investigation of flaky tests

@problame
Copy link
Contributor Author

All flaky test failures found were already tracked as flaky for std-fs in the flaky tests db.

https://neondb.slack.com/archives/C036U0GRMRB/p1706524588253939?thread_ts=1706288637.028629&cid=C036U0GRMRB

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

@problame problame

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jcsp @problame