-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
Subtree update of rust-analyzer
#117701
Subtree update of rust-analyzer
#117701
Conversation
…garding invocation strategy and location
Tested for two cases: 1. Simple Use 2. Complex Use
Subtree update of `rust-analyzer` r? `@HKalbasi`
☀️ Try build successful - checks-actions |
You have to set |
Running |
It's probably unrelated, something about a missing LLVM library. Do I set |
@bors retry |
Subtree update of `rust-analyzer` r? `@HKalbasi`
@bors cancel |
@bors r- |
@bors r=onur-ozkan,HKalbasi |
@bors try- |
You triggered the |
☀️ Test successful - checks-actions |
Finished benchmarking commit (49b27f4): comparison URL. Overall result: ❌ regressions - ACTION NEEDEDNext Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression Warning ⚠: The following benchmark(s) failed to build:
cc @rust-lang/wg-compiler-performance Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 676.64s -> 673.687s (-0.44%) |
Dropping regression label, appears to be noise in the Cargo benchmark (immediately recovered on next commit). |
r? @HKalbasi