Skip to content
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

CI: Test Jupyter Notebooks also on Python 3.10 #425

Merged
merged 4 commits into from
Apr 19, 2024
Merged

Conversation

amotl
Copy link
Member

@amotl amotl commented Apr 18, 2024

About

This patch adjusts CI, in order to optimize testing for Google Colab.

Details

Because we are aiming to run a signifcant portion of the assets here on Google Colab, most notably the Jupyter Notebooks, we may want to follow their cadence of Python updates.

Currently, Google Colab still seems to be on Python 3.10 1, so we may want to adjust the corresponding CI jobs to validate just that, in order to avoid any surprises.

References

Footnotes

  1. https://colab.google/articles/py3.10

@amotl amotl requested review from hammerhead and surister April 18, 2024 21:00
@amotl amotl linked an issue Apr 18, 2024 that may be closed by this pull request
@amotl amotl force-pushed the amo/ci-optimize-for-colab branch from ab42144 to 394f3dc Compare April 18, 2024 21:05
@amotl amotl marked this pull request as ready for review April 18, 2024 21:31
@amotl amotl changed the title CI: Test Jupyter Notebooks on Python 3.10 CI: Test Jupyter Notebooks also on Python 3.10 Apr 18, 2024
@amotl amotl linked an issue Apr 18, 2024 that may be closed by this pull request
amotl added 2 commits April 19, 2024 10:07
This optimizes testing for Google Colab.

Because we are aiming to run a signifcant portion of the assets here on
Google Colab, most notably the Jupyter Notebooks, we may want to follow
their cadence of Python updates.

Currently, Google Colab still seems to be on Python 3.10 [1], so we may
want to adjust the corresponding CI jobs to validate just that, in order
to avoid any surprises.

[1]: https://colab.google/articles/py3.10
The database table `machine_data` has not been made part of the test
infrastructure to reset tables before invoking test cases, causing a
hiccup on developer workstations.
@amotl amotl force-pushed the amo/ci-optimize-for-colab branch from 394f3dc to 141ba89 Compare April 19, 2024 08:10
amotl added 2 commits April 19, 2024 10:18
- Use `REFRESH TABLE` to synchronize data
- Improve formatting around `CONNECTION_STRING`
@amotl amotl force-pushed the amo/ci-optimize-for-colab branch from 141ba89 to b290bae Compare April 19, 2024 08:21
@amotl amotl merged commit 9e66e2c into main Apr 19, 2024
13 of 14 checks passed
@amotl amotl deleted the amo/ci-optimize-for-colab branch April 19, 2024 08:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

TSML: Error in timeseries-anomaly-detection.ipynb Use Python 3.10 on CI, at least for Jupyter Notebooks
2 participants