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

Dummy PR to test coverage test changes in CI #114917

Draft
wants to merge 8 commits into
base: master
Choose a base branch
from

Conversation

Zalathar
Copy link
Contributor

The x86_64-gnu-llvm-15 job that normally runs on PRs doesn't include the profiler runtime, so most of the coverage tests don't get run on PRs.

(That's why #114875 didn't fail until an actual merge was attempted.)

r? @ghost

@rustbot rustbot added A-testsuite Area: The testsuite used to check the correctness of rustc S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. labels Aug 17, 2023
@Zalathar
Copy link
Contributor Author

@rustbot experimental

@Zalathar
Copy link
Contributor Author

@rustbot author

@rustbot rustbot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Aug 17, 2023
@Zalathar
Copy link
Contributor Author

Zalathar commented Aug 17, 2023

@Zalathar
Copy link
Contributor Author

Now testing #114843 in CI on Linux/Windows/macOS, to ensure I don't get any nasty surprises after it's reviewed.

@Zalathar
Copy link
Contributor Author

Success:

@bors
Copy link
Contributor

bors commented Aug 29, 2023

☔ The latest upstream changes (presumably #115183) made this pull request unmergeable. Please resolve the merge conflicts.

@Zalathar Zalathar force-pushed the dummy-coverage branch 2 times, most recently from b605cc7 to c4511d7 Compare September 2, 2023 00:08
@Zalathar
Copy link
Contributor Author

Zalathar commented Sep 2, 2023

Testing #114843 on Linux/Windows/macOS (coverage-map and run-coverage only), to see if everything still works on the big 3 configurations.

@rust-log-analyzer

This comment has been minimized.

@Zalathar
Copy link
Contributor Author

Zalathar commented Sep 2, 2023

Those Linux failures look like the same ones I saw on the aarch64-gnu build, so hopefully that's a platform issue and I don't have to worry about ARM Linux specifically.

I'm going to try another run of Windows only, to flush out any unknown issues on that platform.

@rust-log-analyzer

This comment has been minimized.

@Zalathar
Copy link
Contributor Author

Zalathar commented Sep 2, 2023

Test failures on Windows seem to be the same as the Linux ones, which is surprising.

Perhaps there is some common property of the main Linux/Windows CI environments that is not shared by x86_64-gnu-llvm-15 or my local Aarch64 macOS environment.

@Zalathar
Copy link
Contributor Author

Zalathar commented Sep 2, 2023

I'll try a CI macOS build to double check all the major platforms.

@rust-log-analyzer

This comment has been minimized.

@Zalathar
Copy link
Contributor Author

Zalathar commented Sep 2, 2023

Hmm, so the overall results so far seem to be:

Failure (probably the same failures, though I haven't fully verified this):

  • aarch64-gnu
  • x86_64-gnu
  • x86_64-msvc
  • x86_64-apple-1

Success:

  • x86_64-gnu-llvm-15
  • Local build on aarch64 macOS
  • Local build on aarch64 macOS (--stage=2)

@Zalathar
Copy link
Contributor Author

Zalathar commented Sep 2, 2023

Trying another build with the default PR CI config (x86_64-gnu-llvm-15) just to confirm again that that one still works.

@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@Zalathar Zalathar force-pushed the dummy-coverage branch 2 times, most recently from 56899a2 to d77871f Compare June 21, 2024 10:11
@rust-log-analyzer

This comment has been minimized.

@bors
Copy link
Contributor

bors commented Jun 24, 2024

☔ The latest upstream changes (presumably #126788) made this pull request unmergeable. Please resolve the merge conflicts.

@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@bors
Copy link
Contributor

bors commented Aug 25, 2024

☔ The latest upstream changes (presumably #129295) made this pull request unmergeable. Please resolve the merge conflicts.

This also migrates from legacy `cargo:` directives to the newer `cargo::`
prefix.
This file was introduced in LLVM 11, but was then removed in LLVM 13.
The whole file is surrounded by `#if defined(_WIN32)`, so there's no need to
have separate logic to exclue it from non-Windows builds.
Now that the list of source files has been cleaned up, we can reasonably expect
_all_ of the listed source files to be present.
@bors
Copy link
Contributor

bors commented Sep 19, 2024

☔ The latest upstream changes (presumably #130534) made this pull request unmergeable. Please resolve the merge conflicts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-run-make Area: port run-make Makefiles to rmake.rs A-testsuite Area: The testsuite used to check the correctness of rustc S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants