Skip to content
This repository has been archived by the owner on Mar 7, 2019. It is now read-only.

Test success on version probe #149

Merged
merged 1 commit into from Jan 18, 2016
Merged

Test success on version probe #149

merged 1 commit into from Jan 18, 2016

Conversation

plicease
Copy link
Contributor

If the command fails, but there is some output we get a false positive. This problem was discovered when using perl Build.PL verbose=1 (and demonstrated with Alien::LibYAML). While this exact problem
will hopefully be fixed with PR #147, there are other strangeisms that could infect the captured output with bogus data.

@jberger
Copy link
Member

jberger commented Jan 13, 2016

Yes the command would have to succeed in order to provide useful results I suppose. Aye

@mohawk2
Copy link
Contributor

mohawk2 commented Jan 17, 2016

Currently I am finding it very difficult to make time for open-source stuff. What if we switch our merge policy from "two ayes" to "one aye plus some short delay"?

@plicease
Copy link
Contributor Author

@mohawk2 this is more or less what I have been doing, although "short delay" is seven days. I am happy with this pace.

@mohawk2
Copy link
Contributor

mohawk2 commented Jan 17, 2016

Works for me! I'm also reassured that I'm not holding things up.

If the command fails, but there is some output we get a false positive.
This problem was discovered when using perl Build.PL verbose=1
(and demonstrated with Alien::LibYAML).  While this exact problem
will hopefully be fixed with PR #147, there are other strangeisms
that could infect the captured output with bogus data.
@plicease plicease merged commit cff2ec8 into master Jan 18, 2016
@plicease plicease deleted the check_exit_status branch January 18, 2016 15:53
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

3 participants