Tracking Issue for AppVeyor failures.

[jamestalmage]

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:

• https://github.com/sohamkamani/ava/blob/96121337049337f71ddd4420ab02de548e03c704/test/test.js#L955

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]

PR: #200
Failed Build: https://ci.appveyor.com/project/sindresorhus/ava/build/96
Failed Assertions:

• https://github.com/jamestalmage/ava/blob/732b4c231b7dfd208703dea55713580e0f96e276/test/test.js#L1061
• (this one twice): https://github.com/jamestalmage/ava/blob/732b4c231b7dfd208703dea55713580e0f96e276/test/test.js#L955

Related to stderr / stdout: YES

[jamestalmage]

PR: #205
Failed Build: https://ci.appveyor.com/project/sindresorhus/ava/build/103
Failed Assertions:
(this one twice):
https://github.com/sindresorhus/ava/blob/0529ee2737e48d9e4e22217edcb9c5a10786b16c/test/test.js#L955
Related to stderr/stdout: YES

[jamestalmage]

PR: #206
Failed Build: https://ci.appveyor.com/project/sindresorhus/ava/build/106
Failed Assertions: https://github.com/sindresorhus/ava/blob/a54a6cf28b320359afc7ab5beb302bca079142a3/test/test.js#L1061
Related to stderr/stdout: YES

[jamestalmage]

PR: #209
Failed Build: https://ci.appveyor.com/project/sindresorhus/ava/build/111/job/9jpeuk7w1iqhtgy4#L892
Failed Assertions:
(three times): https://github.com/GabiGrin/ava/blob/baf9e5ca45b8b5d105c1ddfb6ba3c54082406d39/test/test.js#L955
Related to stderr/stdout

[jamestalmage]

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.