-
Notifications
You must be signed in to change notification settings - Fork 126
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
Support --workdir-root
in the tmt clean
command
#2850
base: main
Are you sure you want to change the base?
Conversation
bccb7e3
to
b4e2de6
Compare
1f8d67b
to
8bd2d7f
Compare
8c8da09
to
8d9a62a
Compare
8d9a62a
to
d3ee2a2
Compare
b845dbc
to
caa18b9
Compare
caa18b9
to
4a5c49e
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. Just nitpicks.
I'm surprised setting a workdir root is so complicated tbh (not necessarily related to these changes). :)
@skycastlelily would it be possible to log the workdir root please in case the verbose mode is enabled please? Something like:
|
60409b2
to
ef1cd0f
Compare
Seems the release note adjustment has been lost during rebase, added back in 7a0adc4. Please fetch the latest content from the branch before force-pushing new changes. There is a couple of tests failing:
The error seems to be related:
Please, have a look. Thanks. Not ready for 1.39, moving to 1.40. |
Will keep that on mind:)
I guess it is because my commit to address that error is somehow removed during the rebase,anyway,gonna to have it back:) |
Yeah, that's the problem, added it back:4b61e18.
We have lots of reviews, and commits for this mr, the "new" error is due to the commit to address the error is gone during rebase,hmm,lead, would you please,or do you see any chance we could have this mr released with 1.39 to avoid rebase mess 😿 🥺 ? 😁 |
Sorry for that. I was ready to include it in the release but tests were red. And we cannot postpone the release indefinitely. Let's merge the pull request as one of the first ones in 1.40 to prevent any further rebase problems. |
'--finished', is_flag=True, default=False, | ||
help='List all runs which have all enabled steps completed.') | ||
@verbosity_options | ||
def status( |
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 status definition has been moved to a separate file status.py
. Please, move the changes there.
Pull Request Checklist