-
Notifications
You must be signed in to change notification settings - Fork 5
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
MarkdownProcessingException: -559038737 exit code #163
Comments
A subsequent re-build of the same PR #162 without changes passed - so this is a flaky 😭 https://stackoverflow.com/questions/23370449/jvm-8-exit-code-559038737-0xdeadbeef points out that vorburger/ch.vorburger.exec#9 from (my) It would be good if (a) that If this happens more often, one approach could be to finish the implementation of the alternative |
Actually, no... the initial analysis above is wrong. This is a bug in Enola, maybe a concurency issue? Note how it first logs:
but then
which is clearly inconsistent. |
#165 fixes the misleading diagnostics. It doesn't fix the error that happened on this build, but next time something much clearer will be logged. -- The root cause was that hack in |
Voilà, I just hit this again, this time locally, not on CI:
Not reproducible, and works 2nd time. So a concurrency issue, after all? Missing |
Actually... this will happen in case of the (7s) timeout! But this error message is too confusing, and needs to be improved. |
This includes the following noteworth changes: * vorburger/ch.vorburger.exec#110 * vorburger/ch.vorburger.exec#112 * vorburger/ch.vorburger.exec#115
This includes the following noteworth changes: * vorburger/ch.vorburger.exec#110 * vorburger/ch.vorburger.exec#112 * vorburger/ch.vorburger.exec#115
https://github.com/enola-dev/enola/actions/runs/4930857308/jobs/8812290180?pr=162 for (trivial!) #162 failed 😢 with:
The text was updated successfully, but these errors were encountered: