-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Migrate share-generics-dylib
, raw-dylib-import-name-type
, raw-dylib-link-ordinal
and raw-dylib-stdcall-ordinal
run-make
tests to rmake
#128112
Conversation
This PR modifies cc @jieyouxu |
@bors try |
…=<try> Migrate `share-generics-dylib`, `raw-dylib-import-name-type`, `raw-dylib-link-ordinal` and `raw-dylib-stdcall-ordinal` `run-make` tests to rmake Part of rust-lang#121876 and the associated [Google Summer of Code project](https://blog.rust-lang.org/2024/05/01/gsoc-2024-selected-projects.html). Please try: try-job: x86_64-msvc try-job: x86_64-mingw try-job: test-various
☀️ Try build successful - checks-actions |
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 for the PR. I have a concern about how tests/run-make/raw-dylib-stdcall-ordinal/rmake.rs
is not failing the try job.
.run(); | ||
}; | ||
let out = run("driver").stdout_utf8(); | ||
diff().expected_file("output.txt").actual_text("actual", out).normalize(r#"\r"#, "").run(); |
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.
Problem/Question: this output.txt
is a bit suspicious to me, are we sure this isn't supposed to be expected_output.txt
?
The other test tests/run-make/raw-dylib-link-ordinal
does in fact have a output.txt
, but in this test directory there's only expected_output.txt
.
Or rather, how did this not fail the try job? Am I missing something here?
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.
x86_64-mingw
and x86_64-msvc
: raw-dylib-stdcall-ordinal ... ignored, only executed when the architecture is x86
????????????????
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.
Okay, I replaced it with the seemingly more sensible only-x86_64
.
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.
Problem: actually, sorry I didn't quite register this: if the original test was //@ only-x86
, then this is not more sensible than //@ only-x86_64
, because according to compiletest only-*
directive matching precedence, the matcher that takes precedence for our case here is target architecture precise match, so in this sense x86
is the 32-bit x86 architecture while x86_64
is the 64-bit x86_64 architecture.
1358c84
to
6efba49
Compare
Please run tryjob again. @rustbot ready |
@bors try |
…=<try> Migrate `share-generics-dylib`, `raw-dylib-import-name-type`, `raw-dylib-link-ordinal` and `raw-dylib-stdcall-ordinal` `run-make` tests to rmake Part of rust-lang#121876 and the associated [Google Summer of Code project](https://blog.rust-lang.org/2024/05/01/gsoc-2024-selected-projects.html). Please try: try-job: x86_64-msvc try-job: x86_64-mingw try-job: armhf-gnu try-job: test-various
This comment has been minimized.
This comment has been minimized.
💔 Test failed - checks-actions |
tests/ui/rfcs/rfc-2627-raw-dylib/import-name-type-unknown-value.rs
Outdated
Show resolved
Hide resolved
bee9bda
to
070567a
Compare
Please run try again, on Windows 32 bit this time - ignores are back to 32 bit mode. |
@bors try |
Please r=me if the additional try jobs come back green. |
✌️ @Oneirical, you can now approve this pull request! If @jieyouxu told you to " |
…=<try> Migrate `share-generics-dylib`, `raw-dylib-import-name-type`, `raw-dylib-link-ordinal` and `raw-dylib-stdcall-ordinal` `run-make` tests to rmake Part of rust-lang#121876 and the associated [Google Summer of Code project](https://blog.rust-lang.org/2024/05/01/gsoc-2024-selected-projects.html). Please try: // try-job: i686-msvc // already successful try-job: aarch64-apple try-job: armhf-gnu try-job: test-various try-job: x86_64-msvc try-job: x86_64-gnu-llvm-18
☀️ Try build successful - checks-actions |
@bors r+ rollup=iffy |
☔ The latest upstream changes (presumably #128079) made this pull request unmergeable. Please resolve the merge conflicts. |
r=me with a rebase |
fdb2e90
to
23cccb3
Compare
☀️ Test successful - checks-actions |
Finished benchmarking commit (66e5852): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)Results (secondary -5.9%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 770.467s -> 770.008s (-0.06%) |
Part of #121876 and the associated Google Summer of Code project.
Please try:
// try-job: i686-msvc // already successful
try-job: aarch64-apple
try-job: armhf-gnu
try-job: test-various
try-job: x86_64-msvc
try-job: x86_64-gnu-llvm-18