all InterpError allocate now, so adjust alloc-error-check

[RalfJung]

Cc #82116 (comment)
r? @oli-obk

[RalfJung]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

@rustbot label: +S-waiting-on-perf

[bors]

⌛ Trying commit d496bfc with merge 446a538d70518d147742595eb5df8644ab3fb187...

[bors]

☀️ Try build successful - checks-actions
Build commit: 446a538d70518d147742595eb5df8644ab3fb187 (446a538d70518d147742595eb5df8644ab3fb187)

[rust-timer]

Queued 446a538d70518d147742595eb5df8644ab3fb187 with parent e7c23ab, future comparison URL.

[rust-timer]

Finished benchmarking try commit (446a538d70518d147742595eb5df8644ab3fb187): comparison url.

Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. Please note that if the perf results are neutral, you should likely undo the rollup=never given below by specifying rollup- to bors.

Importantly, though, if the results of this run are non-neutral do not roll this PR up -- it will mask other regressions or improvements in the roll up.

@bors rollup=never
@rustbot label: +S-waiting-on-review -S-waiting-on-perf

[RalfJung]

Some green, some red... I guess that means it's neutral?^^

[oli-obk]

There may be some regressions in max-rss, but it's hard to tell, so in the spirit of simpler code

@bors r+

[bors]

📌 Commit d496bfc has been approved by oli-obk

[bors]

⌛ Testing commit d496bfc with merge 89d32eb...

[bors]

☀️ Test successful - checks-actions
Approved by: oli-obk
Pushing 89d32eb to master...