-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Prepare for new release #1764
Prepare for new release #1764
Conversation
@pradnyeshjoshi we have an issue with the spark tuning code, I don't think it is a problem with this particular PR, but it is annoying |
@miguelgfierro this is weird, I just merged #1763, did not get this error there. |
yeah, I think that precise test is flaky. I have reexecuted the failed jobs again |
@pradnyeshjoshi @anargyri this is annoying, the test failed again. This spark tunning is super flaky:
|
Yes, this is difficult to understand. One thing that is special with this test in particular is that we call |
Added issue about this: #1770 |
@pradnyeshjoshi I have merged staging with your latest changes, hopefully we don't see the error in the tests anymore. Please review this PR |
@miguelgfierro I cannot review this PR, it says I need to be a code owner to review, |
Description
Related Issues
Checklist:
staging branch
and not tomain branch
.