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.

Sign up for GitHub

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

Jump to bottom

Conformance results for v1.20/openstack-magnum #1313

Closed
wants to merge 1 commit into from
Closed

Conformance results for v1.20/openstack-magnum #1313

wants to merge 1 commit into from

Conversation

brtkwr
Copy link
Contributor

@brtkwr brtkwr commented Feb 9, 2021

Pre-submission checklist:

Please check each of these after submitting your pull request:

  • If this is a new entry, have you submitted a signed participation form?
  • Did you include the product/project logo in SVG, EPS or AI format?
  • Does your logo clearly state the name of the product/project and follow the other logo guidelines?
  • If your product/project is open source, did you include the repo_url?
  • Did you copy and paste the installation and configuration instructions into the README.md file in addition to linking to them?

@cncf-ci cncf-ci added release-documents-checked All release documents are present and pass all checks release-v1.20 labels Feb 9, 2021
@cncf-ci
Copy link
Collaborator

cncf-ci commented Feb 9, 2021

Found v1.20 in logs

@cncf-ci
Copy link
Collaborator

cncf-ci commented Feb 9, 2021

This conformance request failed to include all of the required tests for v1.20

@cncf-ci
Copy link
Collaborator

cncf-ci commented Feb 9, 2021

The first test found to be mssing was [sig-scheduling] SchedulerPredicates [Serial] validates that there is no conflict between pods with same hostPort but different hostIP and protocol [LinuxOnly] [Conformance]

@brtkwr brtkwr force-pushed the v1.20/openstack-magnum branch from 65fe51d to fc10c50 Compare February 9, 2021 14:38
@brtkwr
Copy link
Contributor Author

brtkwr commented Feb 9, 2021

I pushed a new patch but the bot is not reacting to it.

@taylorwaggoner taylorwaggoner removed release-documents-checked All release documents are present and pass all checks release-v1.20 required-tests-missing labels Feb 9, 2021
@cncf-ci cncf-ci added the release-documents-checked All release documents are present and pass all checks label Feb 9, 2021
@cncf-ci
Copy link
Collaborator

cncf-ci commented Feb 9, 2021

Found v1.20 in logs

@cncf-ci
Copy link
Collaborator

cncf-ci commented Feb 9, 2021

This conformance request failed to include all of the required tests for v1.20

@cncf-ci
Copy link
Collaborator

cncf-ci commented Feb 9, 2021

The first test found to be mssing was [sig-scheduling] SchedulerPredicates [Serial] validates that there is no conflict between pods with same hostPort but different hostIP and protocol [LinuxOnly] [Conformance]

@brtkwr
Copy link
Contributor Author

brtkwr commented Feb 9, 2021

The bot is wrong, that test is part of the conformance report.

@brtkwr brtkwr closed this Feb 9, 2021
@brtkwr
Copy link
Contributor Author

brtkwr commented Feb 18, 2021

Superseded by #1320

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
release-documents-checked All release documents are present and pass all checks release-v1.20 required-tests-missing
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@brtkwr @cncf-ci @taylorwaggoner