@@ -637,6 +637,26 @@ pub async fn post_finished(data: &InputData) {
637
637
Some ( Direction :: Regression | Direction :: Mixed ) => "+perf-regression" ,
638
638
Some ( Direction :: Improvement ) | None => "-perf-regression" ,
639
639
} ;
640
+ let msg = direction
641
+ . map ( |d| {
642
+ format ! (
643
+ "While you can manually mark this PR as fit \
644
+ for rollup, we strongly recommend not doing so since this PR led to changes in \
645
+ compiler perf.{}",
646
+ match d {
647
+ Direction :: Regression | Direction :: Mixed =>
648
+ "\n \n **Next Steps**: If you can justify the \
649
+ regressions found in this perf run, please indicate this with \
650
+ `@rustbot label: +perf-regression-justified` along with \
651
+ sufficient written justification. If you cannot justify the regressions \
652
+ please fix the regressions and do another perf run. If the next run shows \
653
+ neutral or positive results, the label will be automatically removed.",
654
+ Direction :: Improvement => "" ,
655
+ }
656
+ )
657
+ } )
658
+ . unwrap_or ( String :: new ( ) ) ;
659
+
640
660
post_comment (
641
661
& data. config ,
642
662
commit. pr ,
@@ -647,17 +667,11 @@ pub async fn post_finished(data: &InputData) {
647
667
648
668
Benchmarking this pull request likely means that it is \
649
669
perf-sensitive, so we're automatically marking it as not fit \
650
- for rolling up. Please note that if the perf results are \
651
- neutral, you should likely undo the rollup=never given below \
652
- by specifying `rollup-` to bors.
653
-
654
- Importantly, though, if the results of this run are \
655
- non-neutral **do not** roll this PR up -- it will mask other \
656
- regressions or improvements in the roll up.
670
+ for rolling up. {}
657
671
658
672
@bors rollup=never
659
673
@rustbot label: +S-waiting-on-review -S-waiting-on-perf {}" ,
660
- commit. sha, comparison_url, summary, label
674
+ commit. sha, comparison_url, summary, msg , label
661
675
) ,
662
676
)
663
677
. await ;
0 commit comments