Skip to content

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

Closed
jamestalmage opened this issue Nov 12, 2015 · 5 comments
Closed

Tracking Issue for AppVeyor failures. #197

jamestalmage opened this issue Nov 12, 2015 · 5 comments

Comments

@jamestalmage
Copy link
Contributor

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.

PR: #196
Failed Build: https://ci.appveyor.com/project/sindresorhus/ava/build/89
Failed Assertion:

Related to stderr / stdout: YES

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.

@jamestalmage
Copy link
Contributor Author

@jamestalmage
Copy link
Contributor Author

@jamestalmage
Copy link
Contributor Author

@jamestalmage
Copy link
Contributor Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant