Skip to content

Conversation

@sudohainguyen
Copy link
Collaborator

@sudohainguyen sudohainguyen commented Feb 5, 2024

What this PR does / why we need it:
Following up with NEP and many libraries are dropping py38 support
We need to migrate our CI integration tests to py39+ version

Additional information:

Related to #3928, if we want to run integration tests with pandas v2, we must run on py3.9+,
So that we need to extend our integration tests workflow matrix to run on py310 additionally

Which issue(s) this PR fixes:

Fixes #

@sudohainguyen sudohainguyen changed the title ci: Migrate integration test base python to py39 and py310 Draft: ci: Migrate integration test base python to py39 and py310 Feb 5, 2024
@sudohainguyen sudohainguyen changed the title Draft: ci: Migrate integration test base python to py39 and py310 ci: Migrate integration test base python to py39 and py310 Feb 5, 2024
@sudohainguyen sudohainguyen reopened this Feb 5, 2024
@sudohainguyen sudohainguyen force-pushed the ci branch 4 times, most recently from 1e329f3 to da33350 Compare February 5, 2024 16:04
@sudohainguyen sudohainguyen changed the title ci: Migrate integration test base python to py39 and py310 ci: Extend python base version for test cases Feb 5, 2024
@tokoko
Copy link
Collaborator

tokoko commented Feb 6, 2024

Running integration tests only for 3.10 sounds a bit too risky unless we explicitly drop support for lower versions. I think all tests should include the lowest supported python version (3.8 currently, but if we in fact drop it then 3.9)

@sudohainguyen
Copy link
Collaborator Author

Running integration tests only for 3.10 sounds a bit too risky unless we explicitly drop support for lower versions. I think all tests should include the lowest supported python version (3.8 currently, but if we in fact drop it then 3.9)

actually we still do have full integration tests across 3 python versions on master only (after merged), however I agree that we should extend, not replace for now

Signed-off-by: Hai Nguyen <quanghai.ng1512@gmail.com>
fail-fast: false
matrix:
python-version: [ "3.8" ]
python-version: [ "3.8", "3.10" ]

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this purely adds 3.10 support

- os: macOS-latest
python-version: "3.9"
- os: macOS-latest
python-version: "3.10"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

did you mean to drop 3.10 here?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Drop from exclude list, which means we will conduct py310 unit test on macos

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh i missed the exclude key. Nice.

Copy link
Collaborator

@HaoXuAI HaoXuAI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm!

@HaoXuAI HaoXuAI merged commit 1f3cab8 into feast-dev:master Feb 6, 2024
@sudohainguyen sudohainguyen deleted the ci branch February 6, 2024 05:30
tokoko pushed a commit to tokoko/feast that referenced this pull request Feb 6, 2024
Signed-off-by: Hai Nguyen <quanghai.ng1512@gmail.com>
Signed-off-by: tokoko <togurg14@freeuni.edu.ge>
zseta pushed a commit to zseta/feast that referenced this pull request Feb 7, 2024
Signed-off-by: Hai Nguyen <quanghai.ng1512@gmail.com>
Signed-off-by: Attila Toth <hello@attilatoth.dev>
tqtensor pushed a commit to tqtensor/feast that referenced this pull request Mar 11, 2024
Signed-off-by: Hai Nguyen <quanghai.ng1512@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants