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 bokeh3.4 RC in tests #8565
base: main
Are you sure you want to change the base?
Conversation
Unit Test ResultsSee test report for an extended history of previous test failures. This is useful for diagnosing flaky tests. 27 files ± 0 27 suites ±0 9h 57m 13s ⏱️ + 3m 28s For more details on these failures, see this check. Results for commit 7895a22. ± Comparison against base commit 0438768. ♻️ This comment has been updated with latest results. |
There seem to be a lot of test failures but at least skimming through, they don't appear related to Bokeh at all. I was really just interested in a basic smoke test, i.e. someone who runs the dashboard often to try and update their installed Bokeh to |
OK I dug up my trivial script and AFAICT everything is working 🤷 I do see on deprecation for yall to handle at some point:
In any case I am not going to hold up the planned release Monday unless something else comes up. FYI I did get an error when running this (my previous smoke test) but as far as I can see it's not related to Bokeh at all:
stack trace:
|
20103b5
to
7895a22
Compare
Most of the failures have been resolved on main. I rebased the PR to get a better picture.
This looks as if your workers/scheduler and your client are running on different versions. Maybe your venv is broken? |
@fjetter maybe, as I said I am not a regular Dask user. For ref I created the env like this:
and then |
Bokeh 3.4 has a new release candidate: 3.4.0rc1 . @bryevdv asked that we test before the upcoming release next week.