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
TEST: make and use a fipsinstall script #11565
Conversation
We have copies of the exact same fipsinstall call in several test recipes. This refactors those calls into a single simple script.
Assuming the CIs agree. |
24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set. Please review the updates and set the label manually. |
We have copies of the exact same fipsinstall call in several test recipes. This refactors those calls into a single simple script. Reviewed-by: Paul Dale <paul.dale@oracle.com> (Merged from #11565)
Merged ae6b654 TEST: make and use a fipsinstall script |
@levitte The Travis breakage on OS/X was relevant. |
I'm trying to investigate that. |
use platform; | ||
|
||
my @providers = ($bldtop_dir, 'providers'); | ||
my $fips_cnf = File::Spec->catfile(@providers, 'fipsinstall.cnf'); |
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.
Sigh. This is a a really bad name for the config file. It is about configuration of the FIPS module. I will update my "rename things" PR. :(
We have copies of the exact same fipsinstall call in several test
recipes. This refactors those calls into a single simple script.