-
Notifications
You must be signed in to change notification settings - Fork 60
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
PMI failure log often includes no useful information about failures #192
Comments
Is this PMI specific? I'm pretty sure I've seen a similar issue with non-PMI diffs - if the JIT asserts the assert output is no where to be found. |
Not sure. Looking at it now. |
PMI writes a .err file to the CWD named after the assembly, but it's no more helpful.
Seems like if DRIVEALL can't auto-diagnose the error (so we can retry to get past asserts) it should just spew out the subprocess stream. And we should have this end up in the same place as the log file (or be part of the log file). |
I did a quick test with crossgen - the assert text does go to |
Actually no, I take that back. Redirecting stderr (via the Process class) works fine. |
Apparently |
Turns out that in my case it's just that I'm using the Release VM with a Checked JIT. In that case the JIT calls But I see that you're using a checked VM. If I do that (with either PMI or crossgen) I do see the JIT assert in the log file produced by jit-dasm. |
eg:
has failure log:
The text was updated successfully, but these errors were encountered: