-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Tracking Issue for AppVeyor failures. #197
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
Comments
PR: #200
Related to stderr / stdout: YES |
PR: #205 |
PR: #206 |
PR: #209 |
This has adequately demonstrated that it's random errors with stdout / stderr not getting the complete output. The fix is known and submitted. No need to track errors anymore. |
Please Keep Chatter On This Thread Minimal
I intend to use this to track AppVeyor failures and hopefully hunt down the problem. So far it seems random.
If you submit a PR that fails and you want to help me out, please post the following.
Please note that the
Failed Assertion
link is to a particular commit. Linking to master is less helpful because line numbers change over time.The
related to stderr/stdout
line is just a simple yes/no answer if the failed assertion had something to do with stderr/stdout from a forked process.The text was updated successfully, but these errors were encountered: