-
Notifications
You must be signed in to change notification settings - Fork 70
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
Fix combination beaker names and hosts #800
Conversation
ci-linchpin-messageBus-trigger build #582: FAILURE: https://jenkins-continuous-infra.cloud.continuous-infra.upshift.redhat.com/job/ci-linchpin-messageBus-trigger/582/ |
Can one of the admins verify this patch? |
Previously, each name was combined with each host. This fixes the function so that each name is paired with the corresponding host Signed-off-by: Ryan Cole <rycole@redhat.com>
5254ebb
to
5bb7cf6
Compare
@14rcole Could you add sample unit test with mock data to check if works or not ? |
@p3ck @samvarankashyap ptal |
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
@samvarankashyap sorry, I didn't see your comment. I can. This would fall under #798 though, should I just put the unit test in there with the rest or slip it in here? |
ci-linchpin-messageBus-trigger build #585: SUCCESS: https://jenkins-continuous-infra.cloud.continuous-infra.upshift.redhat.com/job/ci-linchpin-messageBus-trigger/585/ |
You can group it with others |
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
[merge] |
Previously, each name was combined with each host. This fixes the function so that each name is paired with the corresponding host