ci: addition of downstream tests for bokeh #2762
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
wow, thanks! these "downstream-slow" tests don't run by default, do we have a way to trigger them? do you know how long this ci job takes? |
|
The overall CI job takes about 10 minutes to complete. I didn’t realized how many time the ci jobs in the slow file takes in the execution (more than 20 minutes). Because of the difference in the execution time, I moved the bokeh’s jobs to the For context, this 10-minute duration for the Bokeh CI job is similar to what we see with the Narwhals |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this? (check all applicable)
Related issues
Checklist
If you have comments or can explain your changes, please do so below
Hi @MarcoGorelli !
For the CI, I've mirrored the testing approach from the original Bokeh repository. This helps tolerate potential changes in their conda environment YAML files. While this method is a bit verbose, I can certainly explore a simpler approach if preferred.