-
Notifications
You must be signed in to change notification settings - Fork 301
Give types team members access to perf, crater and dev-desktops. #963
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
Conversation
5512ad0
to
d1dded6
Compare
+1 from me |
@@ -39,3 +39,7 @@ extra-people = ["eholk"] | |||
|
|||
[permissions] | |||
bors.chalk.review = true | |||
bors.rust.try = true | |||
perf = true | |||
crater = true |
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.
Crater runs don't happen super often. Given that they take a large amount of expensive machinery to run it seems reasonable to limit its use. Is there any reason the types team members can't reach out to a compiler team member when this is needed?
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.
Crater runs don't happen super often
Types team members run crater far more frequently than most other compiler contributors.
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.
Sounds find to me. cc @Mark-Simulacrum and @pietroalbini
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'm fine with types having crater access.
Co-authored-by: Ali MJ Al-Nasrawy <[email protected]>
Not all our members are compiler-contributors, compiler or other similar team members.
In rust-lang/rust#109388 (comment) @aliemjay was unable to run perf.