Skip to content

(DO NOT MERGE): Reliable output #213

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

Conversation

jamestalmage
Copy link
Contributor

This combines:
#206
#208
#211

In hopes that the combined strategies are the answer to brittle AppVeyor tests.

DO NOT MERGE:
Over time this PR Became a dump for every random thought I had on how to make AppVeyor work. I need to keep it open so AppVeyor continues to build, but once I find a reliable strategy, I will submit separate, cleaner PR's.

@jamestalmage jamestalmage force-pushed the wait-for-forked-streams-2 branch from 4cfeee9 to effb4ef Compare November 14, 2015 05:56
@jamestalmage jamestalmage force-pushed the wait-for-forked-streams-2 branch from b2697b3 to 2e6031f Compare November 14, 2015 06:46
@jamestalmage jamestalmage changed the title Reliable output (DO NOT MERGE): Reliable output Nov 14, 2015
@jamestalmage
Copy link
Contributor Author

closing in favor of #206

@jamestalmage jamestalmage deleted the wait-for-forked-streams-2 branch November 21, 2015 23:43
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

Successfully merging this pull request may close these issues.

2 participants