-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Test failed: System.Diagnostics.StackTrace.Tests #36585
Comments
It's marked no inlining: private class ClassWithConstructor
{
public StackFrame StackFrame { get; }
[MethodImpl(MethodImplOptions.NoInlining)]
public ClassWithConstructor() => StackFrame = new StackFrame();
} |
That one is, but I don't think that's the right one. This one is missing it:
The fix is likely to add NoInlining to that ctor. |
This raises an interesting question. In release builds / runs, are most of our tests (the tests themselves) running unoptimized because they're generally only executed once and thus they won't be promoted from tier 0? |
@stephentoub That's my belief, which is worrisome (I've expressed this worry before; don't remember to whom). cc @AndyAyersMS I'm planning to add back JIT stress mode testing over libraries (including simply no-tiering mode) with #36486, but it's worth considering whether a more regular mode, e.g., libraries PR or CI, should do this as well. |
I'm trying to enable libraries testing using checked coreclr and JIT stress modes. This test fails when disabling TieredCompilation (meaning we're actually optimizing)
Is this a case where the test is expecting a certain set of inlining (or no inlining) that is invalid?
@stephentoub ?
The text was updated successfully, but these errors were encountered: