Fix loading target specs in compiletest not working with custom targets#113200
Fix loading target specs in compiletest not working with custom targets#113200bors merged 1 commit intorust-lang:masterfrom
Conversation
|
@bors r+ p=1 unblocks local development with mir blessing Thanks! ❤️ |
|
⌛ Testing commit 00cc815 with merge b7c812b2a52ff293140a718210d069e05a943c86... |
|
The job Click to see the possible cause of the failure (guessed by this bot) |
|
💔 Test failed - checks-actions |
|
@bors retry mips segfault |
|
☀️ Test successful - checks-actions |
|
Finished benchmarking commit (f4b80ca): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. 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: 660.386s -> 660.64s (0.04%) |
In #112454 (comment) it was pointed out that the PR broke blessing mir-opt tests. Since #112418, blessing mir-opt tests generates "synthetic targets", which are custom target specs. Those specs are not included in
--print=all-target-specs-json, and #112454 required that the current target was returned by that flag.This PR fixes the breakage by loading the target spec for the current target explicitly, if a custom target is detected.
r? @oli-obk