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
Do not write artifacts to current dir in tests #749
Do not write artifacts to current dir in tests #749
Conversation
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.
Approving because most of my comments are nitty.
/lgtm
A lot of the tests would create artifacts folders in the directory under test. They would also create preflight.log in those same locations. This makes sure that that does not occur. It also removes the side effect from the artifacts.Path() call. That call would create the artifacts dir, and that's just very unexpected. Instead, this moves the dir creation side effect into the artifacts.WriteFile() call, which is much more an expected behaviour. Signed-off-by: Brad P. Crochet <brad@redhat.com>
91f4f54
to
d75ca0f
Compare
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: acornett21, bcrochet, komish The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
A lot of the tests would create artifacts folders in the directory
under test. They would also create preflight.log in those same
locations. This makes sure that that does not occur.
It also removes the side effect from the artifacts.Path() call.
That call would create the artifacts dir, and that's just very
unexpected. Instead, this moves the dir creation side effect into
the artifacts.WriteFile() call, which is much more an expected
behaviour.
Signed-off-by: Brad P. Crochet brad@redhat.com