Skip to content
This repository has been archived by the owner on May 3, 2023. It is now read-only.

Python 3.10 Wheels #152

Merged
merged 28 commits into from
Aug 27, 2021
Merged

Python 3.10 Wheels #152

merged 28 commits into from
Aug 27, 2021

Conversation

lithomas1
Copy link
Contributor

@lithomas1 lithomas1 commented Aug 21, 2021

xref pandas-dev/pandas#42946

(this also needs a whatsnew, pls don't close the issue)

@lithomas1
Copy link
Contributor Author

Well this looks working now. I think the builds are flaking out again, anyone(with write access) want to restart them(I could close/reopen but that wastes a ton of build minutes)?

cc @simonjayhawkins @jreback

@lithomas1 lithomas1 marked this pull request as draft August 22, 2021 15:19
@lithomas1
Copy link
Contributor Author

lithomas1 commented Aug 22, 2021

Ok this should be green now for travis also. Have also confirmed that the other 32 bit builds aren't flaking out and seems to also be an actual failure on master, so I'll upgrade/fix them later in another PR.

travis failed because of a flakeout on py 3.7, the py 3.10 build on their is fine. Let's just restart all non 32-bit flaky jobs just to be sure.

@lithomas1 lithomas1 marked this pull request as ready for review August 22, 2021 23:29
Copy link
Collaborator

@simonjayhawkins simonjayhawkins left a comment

Choose a reason for hiding this comment

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

Thanks @lithomas1

.travis.yml Outdated
@@ -60,7 +69,15 @@ script:
- source multibuild/travis_steps.sh
- source extra_functions.sh
- setup_test_venv
- install_run $PLAT
# pandas-dev/pandas#41935, we get weird numpy
# failures on python 3.10
Copy link
Collaborator

Choose a reason for hiding this comment

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

This is not failing on pandas ci?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It was, but we just made the CI allowed to fail. The failed tests are visible when you look at the logs of any Python 3.10 run I believe.

Copy link
Collaborator

Choose a reason for hiding this comment

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

we just made the CI allowed to fail

maybe the failing tests should be XFAILed instead?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

There are a lot of flaky ones unfortunately, which is why the build is just allowed to fail.

.travis.yml Outdated
- if [ "$MB_PYTHON_VERSION" == "3.10" ]; then
set +e;
install_run $PLAT;
exit 0;
Copy link
Collaborator

Choose a reason for hiding this comment

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

how many tests are failing? can we just update function run_tests in config.sh to skip those tests? we do this for others.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm actually not too sure. The failures here are different than those in the main repo. It seems though like its the same group of 23 tests failing here, though. I'll try to update when I have time later.

@lithomas1
Copy link
Contributor Author

@simonjayhawkins This should be ready now. Not removing the other code that makes CI pass since we could have different failing tests on master(this PR builds on 1.3.2). I'll try to follow up on this.

(Travis build canceled, but the last one passed. The last commit is just modifying a comment).

@simonjayhawkins
Copy link
Collaborator

@simonjayhawkins This should be ready now. Not removing the other code that makes CI pass since we could have different failing tests on master(this PR builds on 1.3.2). I'll try to follow up on this.

Thanks @lithomas1 . I would prefer not to have the extra code but also want to see the 3.10 wheels built on nightly sooner.

since nightly is built from master is it worth temporarily changing BUILD_COMMIT="master" here, doing the changes here, and then changing it back before merge?

Copy link
Collaborator

@simonjayhawkins simonjayhawkins left a comment

Choose a reason for hiding this comment

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

Thanks @lithomas1 lgtm

NTERNALERROR> assert not 'tests/base/test_unique.py::test_unique_bad_unicode[idx_or_series_w_bad_unicode1]' seen before. restarted to be sure. ping on green

@lithomas1
Copy link
Contributor Author

@simonjayhawkins As green as it gets, I guess. 3.7 linux flaked out again with a different but still flaky error.

@simonjayhawkins simonjayhawkins merged commit 2e9a1d0 into MacPython:master Aug 27, 2021
@simonjayhawkins
Copy link
Collaborator

Thanks @lithomas1

@lithomas1 lithomas1 deleted the patch-1 branch November 13, 2021 21:28
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants