-
Notifications
You must be signed in to change notification settings - Fork 54
Add test for 'yes' #992
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
Add test for 'yes' #992
Conversation
Runs yes as child process with parent reading ten lines. May be run on alternative yes programs for comparison.
|
Hmm – looks like the Appveyor ubuntu2004 build failed! That's a surprise ... I'm guessing the child process got blocked somehow. I specifically wrote it to perform a unidirectional read so I didn't expect that to be a problem. |
briandfoy
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The test looks good, but I think you have an extra file in this commit. Did you mean to include t/yes/yes?
t/yes/yes
Outdated
| @@ -0,0 +1,47 @@ | |||
| #!/usr/bin/env perl | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you mean to commit this file?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello brian, many thanks. I certainly did not! What a howler. Fix imminent.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
File removed.
|
I'll give you about a week to respond, and failing that I'll fix up the pull request and merge it. |
|
This will be part of the next release, which might be a bit. Thanks, |
This PR adds a test for the
/bin/yesscript.I hope this may be considered useful even though 'yes' is a very simple program. My intention was partly to complete an easy task with a view to hopefully making more substantial contributions in future.
I have attempted to write it cogently and adapt it to the house style, but suspect I have come up short on both counts.
I could not find a standing dev branch so have targeted master, but can easily target a different branch if desired.
Should this humble contribution is of interest to the project, I would be honoured to receive any and all feedback, whether detailed or e.g. just 'go back and look at these guidelines again' or 'run perltidy with this config'.
In particular, I will quite understand if you would prefer this rebased into a single commit.
I have run it with
provefrom my forked repo's root, and it seemed to play well with the other tests, but do let me know if I have missed some complete howlers.Best wishes and thanks.