-
Notifications
You must be signed in to change notification settings - Fork 28
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
Test case 301 to case 400 - Jc #344
Conversation
@jguipi You need rebase this pull request with latest master branch. Please check. |
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.
These test cases have been validated success against aws/gcp/azure on k8s 1.20.4, hence moving it from skip.json to working.json
I think you missed to add the testcases in the working.json?
They are just removed from the skip.json.
When you add the testcases can you also check their execution times and categorize them respectively (tests that are faster than 2minutes belong to the fast
group all others to the slow
group)
Done :) ! |
Hi @jguipi , are you sure that we go down from ~434 tests in working.json vs now some 34 ones? |
filtering test case adding groups
Was missing the data from the upstream. IJust merge and rebase it all |
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
What this PR does / why we need it:
These test cases have been validated success against aws/gcp/azure on k8s 1.20.4, hence moving it from skip.json to working.json
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note: