-
Notifications
You must be signed in to change notification settings - Fork 521
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
tough async #3566
tough async #3566
Conversation
Update PR to released version of tough async. |
This refactor of test code will make it easier to switch to async since the tokio::fs::read_dir API does not match the std::fs::read_dir API.
Would be good to triage the errors on downgrade for the host-containers migration. |
I have confirmed that this happens when running a |
Issue number:
Description of changes:
Use
tough
in itsasync
incarnation.Testing done:
tough
with these changes.Note: during the re-test, when I looked at migrator's jounral entries I saw some errors on downgrade. This is was v1.15.1 which was built from the tag (and thus not running the new async code).
On upgrade (running the new async code) I did not see these errors. For the purposes of these PRs, the testing shows that migrator is working correctly. Someone may want to look into the host container migrations on downgrade to see what's up.
Terms of contribution:
By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.