-
Notifications
You must be signed in to change notification settings - Fork 669
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
Migrate all e2es to run descheduler as an image #1478
Comments
@jklaw90 @JaneLiuL @fanhaouu @pravarag @eminaktas @zhifei92 @googs1025 in case you would like to contribute |
Not sure if there is an ETA, I can make some contributions. @ingvagabund |
There's no ETA. Also, there's no guarantee the issue will stay unresolved for long. I will eventually migrate all the e2es to simplify #1466. |
ok |
Hi @ingvagabund |
@hsunwenfang thank you. Any of the listed items is currently for taking. |
I have completed some E2E tests, but encountered some issues when running the E2E tests locally. I am still debugging and working on resolving them. |
Hi @ingvagabund |
Can you provide more information? If you are working on this issue, you can also raise a WIP PR to ask the question. |
Hi @googs1025 |
@hsunwenfang dropped comments in the wip pr :) @fanhaouu do the issues reproduce only locally? |
In theory, it should also exist online. There's an issue with some of the code you wrote. I'll make some adjustments, and you can review it later.For example, the current container E2E test didn't meet expectations, but it still shows as 'pass'. |
done: #1500 |
With #1474 we can run the descheduler through a pod. End-to-end testing is not intended to run the descheduler code directly, as this does not accurately reflect its operation in production.
Each e2e test can be refactored separately. #1472 is an example of the first step running the descheduler as a whole. While #1474 gives idea on how to run it as a deployment.
The following e2es need to be migrated:
The text was updated successfully, but these errors were encountered: