-
Notifications
You must be signed in to change notification settings - Fork 338
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
Disable UTs for APB Temporarily. #3741
Conversation
I see unidling tests flaking:
if i see a second one I am going to open an issue: https://github.com/ovn-org/ovn-kubernetes/actions/runs/5451066748/jobs/9917243947?pr=3741 |
May I suggest an alternative option to use XDescribe
Instead of commenting the code? This options still has an exit code of 0 for the test and it reports the tests as pending rather than gone:
Rather than:
when running all the tests (assuming none is commented out). |
yes as discussed in meeting will use |
658639b
to
fc5ca9b
Compare
@jcaamano : this one is good once CI passes. |
@tssurya should the failing tests be disabled?
|
@jcaamano : I think those are fine, if e2e's are failing since its a separate lane anyways people can ignore the whole lane.. the UTs are the ones blocking other PRs. cc @npinaeva @jordigilh : saving the e2e failure link here in case its useful: https://github.com/ovn-org/ovn-kubernetes/actions/runs/5462546420/jobs/9943298187?pr=3741 |
fc5ca9b
to
d5d3506
Compare
Disable UTs for APB Temporarily till the feature is stabilized. Reason: UTs are very flaky. Each PR is needed a minimum of 3 close/open combinations and luck for CI to pass to even run e2e's. At this stage where other features are trying to get in before the deadline this process is painful. Signed-off-by: Surya Seetharaman <[email protected]>
d5d3506
to
4a24833
Compare
|
I don't have permissions to do anything else. |
ahhh :( thanks @jcaamano for getting to this! |
- What this PR does and why is it needed
Disable UTs for APB Temporarily till the feature
is stabilized.
Reason: UTs are very flaky. Each PR is needed a
minimum of 3 close/open combinations and luck for CI
to pass to even run e2e's. At this stage where other features
are trying to get in before the deadline this process is painful.
At least if the retest flag was present it would be nice, closing/opening
PRs on github frequently - we don't know what the consequences of that
for bigger feature PRs are.. too muc of time consumption trying to get CI
to pass
cc @jordigilh : WDYT? I think you and @npinaeva are working to get it all fixed
but that may take 2 more weeks for merge, meanwhile I'd like to unblock CI.
cc @jcaamano