Add `@bors perf` command or similar
See original GitHub issueThe typical workflow when having to get perf data for a commit is
@bors try
(wait until bors posts that it is done)
@rust-timer build SHA
(wait until that is done)
It would be great if bors would have a command like perf
, that would work basically exactly the same as try
, except that the “try build done” message would invoke the rust-timer bot the same way that we currently have to do manually (yay, bots calling bots). So, no human interaction should be needed, after doing @bors perf
, until the final perf results are in.
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Linux perf: How to Use the Command and Profiler - phoenixNAP
Learn how to use the Linux perf command to profile, count, and analyze system events and CPU performance in this guide.
Read more >Getting started with the perf command - IBM
The perf command can report combinations of performance counters as performance metrics and can inject small scripts (BPF scripts) into the kernel to...
Read more >Tutorial - Perf Wiki
The perf tool offers a rich set of commands to collect and analyze performance and ... Each event is added to the same...
Read more >Issues - GitHub
Create a test-perf command in test_commands.py to bootstrap the test env and run. Pretty print the test result for human to read ( ......
Read more >Linux perf Examples - Brendan Gregg
The perf tool is in the linux-tools-common package. Start by adding that, then running "perf" to see if you get the USAGE message....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It would probably be better to add this to rust-timer itself?
I don’t think we can do better than that personally (or should, perhaps). So closing.