-
Notifications
You must be signed in to change notification settings - Fork 11.4k
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
[test-infra][2/n] Replace Move's .exp tests with cargo-insta #21004
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look good to me, although I didn't go through every single snap file...
Just a couple little nits where things might be able to be cleaned up.
external-crates/move/crates/move-compiler/tests/move_check_testsuite.rs
Outdated
Show resolved
Hide resolved
external-crates/move/crates/move-compiler/tests/move_check_testsuite.rs
Outdated
Show resolved
Hide resolved
let p; | ||
let test_name = { | ||
p = path.with_extension(""); | ||
assert!(p.extension().is_none()); | ||
p.file_name().unwrap().to_string_lossy() | ||
}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe this is equivalent to
let test_name = path.file_stem().unwrap().to_string_lossy().as_ref();
and that might be a bit cleaner?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! I was looking for this!
I went through all of them... But all of the configurations should be correct. And otherwise no changes to the compiler! |
9bacc24
to
87e3830
Compare
Description
Test plan
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.