Skip to content
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

Crucible | Update possible responses received from KVM Force Power On System #115

Merged
merged 7 commits into from
Jan 5, 2024

Conversation

ramperher
Copy link
Contributor

@ramperher ramperher commented Jan 4, 2024

Test-Hints: assisted-abi

@ramperher ramperher requested a review from a team as a code owner January 4, 2024 10:59
@ramperher ramperher requested a review from tkrishtop January 4, 2024 10:59
@ramperher
Copy link
Contributor Author

CC @tkrishtop

@dcibot
Copy link
Collaborator

dcibot commented Jan 4, 2024

Starting dci-check-change job.

Copy link

@ramperher
Copy link
Contributor Author

I don't get the point of the failure in the Pull Request / Ansible-lint Check (pull_request), since it's complaining about code that is not being changed in this PR. I suppose that, after a green job, it should be fine to merge this.

@dcibot
Copy link
Collaborator

dcibot commented Jan 4, 2024

@dcibot
Copy link
Collaborator

dcibot commented Jan 4, 2024

Starting dci-check-change job.

Copy link

Copy link
Contributor

@tkrishtop tkrishtop left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ramperher if you want to move the commits from one PR to another, it's better to use git cherry-pick comment_hash to avoid merge conflicts and to keep the author. Thanks.

@dcibot
Copy link
Collaborator

dcibot commented Jan 4, 2024

@dcibot
Copy link
Collaborator

dcibot commented Jan 4, 2024

Starting dci-check-change job.

Copy link

@dcibot
Copy link
Collaborator

dcibot commented Jan 4, 2024

@dcibot
Copy link
Collaborator

dcibot commented Jan 4, 2024

Starting dci-check-change job.

@dcibot
Copy link
Collaborator

dcibot commented Jan 4, 2024

@ramperher ramperher requested a review from tkrishtop January 4, 2024 14:01
@dcibot
Copy link
Collaborator

dcibot commented Jan 4, 2024

Starting dci-check-change job.

@ramperher
Copy link
Contributor Author

@ramperher if you want to move the commits from one PR to another, it's better to use git cherry-pick comment_hash to avoid merge conflicts and to keep the author. Thanks.

Wow, I was not aware of this, thanks for the recommendation. I've applied that and now your commit from the other PR is in this one, then I've corrected what was required, regarding the URL.

Copy link

@ramperher ramperher force-pushed the crucible-kvm-power-on branch from 17d8779 to f5bbd20 Compare January 4, 2024 14:46
@dcibot
Copy link
Collaborator

dcibot commented Jan 4, 2024

@dcibot
Copy link
Collaborator

dcibot commented Jan 4, 2024

Starting dci-check-change job.

Copy link

@tkrishtop
Copy link
Contributor

@ramperher if you want to move the commits from one PR to another, it's better to use git cherry-pick comment_hash to avoid merge conflicts and to keep the author. Thanks.

Wow, I was not aware of this, thanks for the recommendation. I've applied that and now your commit from the other PR is in this one, then I've corrected what was required, regarding the URL.

Let's do git revert fd97ce740ebea5b49d425b7c64aacffc67fd1cba as well. Currently, this commit is modifying the same line in priority and may produce a merge conflict: fd97ce7

@dcibot
Copy link
Collaborator

dcibot commented Jan 4, 2024

@dcibot
Copy link
Collaborator

dcibot commented Jan 4, 2024

  • dci-check-change preparation : FAILURE tested on libvirt:assisted-abi

@ramperher
Copy link
Contributor Author

@ramperher if you want to move the commits from one PR to another, it's better to use git cherry-pick comment_hash to avoid merge conflicts and to keep the author. Thanks.

Wow, I was not aware of this, thanks for the recommendation. I've applied that and now your commit from the other PR is in this one, then I've corrected what was required, regarding the URL.

Let's do git revert fd97ce740ebea5b49d425b7c64aacffc67fd1cba as well. Currently, this commit is modifying the same line in priority and may produce a merge conflict: fd97ce7

Done

@dcibot
Copy link
Collaborator

dcibot commented Jan 4, 2024

Starting dci-check-change job.

Copy link

@dcibot
Copy link
Collaborator

dcibot commented Jan 4, 2024

@ramperher
Copy link
Contributor Author

Change is working and it's ready for review, CC @tkrishtop and @nocturnalastro

Copy link
Contributor

@tkrishtop tkrishtop left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks @ramperher

@ramperher ramperher merged commit b2a4b70 into main Jan 5, 2024
6 checks passed
@ramperher ramperher deleted the crucible-kvm-power-on branch January 5, 2024 10:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants