-
Notifications
You must be signed in to change notification settings - Fork 344
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
Extended environment variable control #5901
Conversation
ea2b571
to
4e94704
Compare
Hi @dgibson, please have a look and let me know if this satisfies pasta needs from #5901. You can look at documentation which describes environment variable control. |
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.
b1625d7
to
5a6f95d
Compare
Hi @clebergnu I have applied changes based on your proposals. Please have a look. |
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.
Hi @richtja,
Thanks for this second version! I've spotted a few extra things though.
5a6f95d
to
697361b
Compare
Hi @clebergnu thank you very much for your review, It was really helpful. I addressed your comments in |
So far, we don't really have much in the way of requirements here. I suggested something like this to Cleber, because I think long term it's something we'll want, and makes for a more generally useful way of running these "extended exec" tests from Avocado. I'll review as best I can. |
697361b
to
1b83ecb
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.
This version LGTM. Before merging, I'm asking @dgibson to ACK it too, since he participated a lot in the review and has great interest in the actual result.
1b83ecb
to
24f821f
Compare
Hi @clebergnu and @dgibson I have updated this PR, to cover also option (1) from #5901 (comment). Now the |
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.
In terms of the design and functionality exposed this LGTM.
I still see a few nits in the implementation, for which I've left comments.
Signed-off-by: Jan Richter <[email protected]>
This commit updates avocado documentation to describe defining environment variables in exec-tests by user. Signed-off-by: Jan Richter <[email protected]>
This commit adds more control over the environment variables in exec-tests for users. It brings a way how to disable env variable during the test runtime so it won't be available to test script. Only thing which user needs to do is to set the variable to `None` in test `kwargs`. Reference: avocado-framework#5889 Signed-off-by: Jan Richter <[email protected]>
24f821f
to
a8b2390
Compare
Hi @dgibson, thank you for your review. I did an update base on your comments. Please have a look.
|
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, thanks!
Updates LGTM. Only remaining nit is the question about whether we're really testing the |
This commit adds more control over the environment variables in exec-tests for users. It brings a way how to clear the test environment during the test runtime so it won't affect the test script. Only thing which user needs to do is to set the runner.exectest.clear_env to `system` or `all` in tests config. Reference: avocado-framework#5889 Signed-off-by: Jan Richter <[email protected]>
a8b2390
to
112dd07
Compare
Hi @dgibson I have split the |
@richtja well.. I'm trying to ack the latest version, but github appears to be messing up. I hit "submit review" and the cursor changes, but it never appears to actually go through. In any case, it LGTM now. Thanks for the |
Thank you, I am merging it now. |
This PR adds more control over the environment variables in exec-tests for users. It brings a way how to disable one env variable or clear the whole environment during the test runtime so it won't be available to test script.