Skip to content
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

Fix Appveyor testing: the format of this flametest doesn't matter #6808

Merged
merged 1 commit into from Jan 30, 2018

Conversation

lamont-granquist
Copy link
Contributor

we don't need to test the exact output of this powershell command, just
get literally anything that looks like it ran successfully.

we don't need to test the exact output of this powershell command, just
get literally anything that looks like it ran successfully.

Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
@lamont-granquist lamont-granquist requested a review from a team January 30, 2018 01:44
@lamont-granquist lamont-granquist changed the title the format of this flametest doesn't matter Fix Appveyor testing: the format of this flametest doesn't matter Jan 30, 2018
@lamont-granquist lamont-granquist merged commit a470cea into master Jan 30, 2018
@lamont-granquist lamont-granquist deleted the lcg/fix-powershell-out branch January 30, 2018 02:24
@lamont-granquist
Copy link
Contributor Author

there's still rubygems issues on appveyor + the epic_fail unit test.

@lock
Copy link

lock bot commented Apr 14, 2018

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.

@lock lock bot locked and limited conversation to collaborators Apr 14, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants