-
Notifications
You must be signed in to change notification settings - Fork 162
Attach test environment to its invocation #4452
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
base: main
Are you sure you want to change the base?
Conversation
9b129e8 to
6d96626
Compare
252dce7 to
bbf844d
Compare
35e6411 to
1263261
Compare
1263261 to
f0f4627
Compare
|
/packit restart-failed |
tcornell-bus
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.
LGTM
tmt/steps/execute/__init__.py
Outdated
| import abc | ||
| import copy | ||
| import functools | ||
| import itertools |
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.
I don't see itertools being used?
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.
Hmmm, unused indeed, but why is no linter complaining? Fixed in c397570.
This will present the same environment to all users of test invocation, from checks to test itself and its results. It was also not clear who is responsible for the environment and its composition, now when it's part of the invocation, all `execute` plugins should see the same content.
f0f4627 to
c397570
Compare
This will present the same environment to all users of test invocation, from checks to test itself and its results. It was also not clear who is responsible for the environment and its composition, now when it's part of the invocation, all
executeplugins should see the same content.Pull Request Checklist