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

upgrade tokio 1.34 => 1.36 #7008

Merged
merged 1 commit into from
Mar 4, 2024
Merged

upgrade tokio 1.34 => 1.36 #7008

merged 1 commit into from
Mar 4, 2024

Conversation

problame
Copy link
Contributor

@problame problame commented Mar 4, 2024

tokio 1.36 has been out for a month.

Release notes don't indicate major changes.

Skimming through their issue tracker, I can't find open C-bug issues that would affect us.

(My personal motivation for this is JoinSet::try_join_next.)

tokio 1.36 has been out for a month.

Release notes don't indicate major changes.

Skimming through their issue tracker, I can't find open `C-bug` issues
that would affect us.

(My personal motivation for this is `JoinSet::try_join_next`.)
@conradludgate
Copy link
Contributor

Proxy recently forked copy_bidirectional, which had some changes since. Notably only cooperative budget stuff. Potentially need to make some changes there, but nothing blocking tokio-rs/tokio#6250

Copy link

github-actions bot commented Mar 4, 2024

2484 tests run: 2362 passed, 0 failed, 122 skipped (full report)


Flaky tests (1)

Postgres 14

  • test_pg_regress[4]: debug

Code coverage* (full report)

  • functions: 28.7% (6935 of 24172 functions)
  • lines: 47.2% (42529 of 90097 lines)

* collected from Rust tests only


The comment gets automatically updated with the latest test results
762828e at 2024-03-04T16:52:22.559Z :recycle:

@arpad-m arpad-m merged commit e62baa9 into main Mar 4, 2024
53 checks passed
@arpad-m arpad-m deleted the problame/upgrade-tokio branch March 4, 2024 17:36
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

3 participants