Skip to content

Tracking Issue for shuffle and shuffle-seed #89583

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

Open
1 of 3 tasks
smoelius opened this issue Oct 6, 2021 · 1 comment
Open
1 of 3 tasks

Tracking Issue for shuffle and shuffle-seed #89583

smoelius opened this issue Oct 6, 2021 · 1 comment
Labels
A-libtest Area: `#[test]` / the `test` library C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.

Comments

@smoelius
Copy link
Contributor

smoelius commented Oct 6, 2021

This is a tracking issue for unstable libtest options --shuffle and --shuffle-seed.

These options allow tests to be run in random order, as opposed to the default alphabetical order.

Steps / History

Unresolved Questions

  • None yet.
@smoelius smoelius added C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. labels Oct 6, 2021
@camelid camelid added the A-libtest Area: `#[test]` / the `test` library label Oct 8, 2021
@smoelius
Copy link
Contributor Author

smoelius commented Oct 8, 2021

Following up on #89082 (comment) (cc: @joshtriplett).

This appears to be the commit that introduced lld's --shuffle-sections: llvm/llvm-project@d48d339

Here are some differences I noticed between their implementation and ours:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-libtest Area: `#[test]` / the `test` library C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
Projects
Status: No status
Development

No branches or pull requests

2 participants