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
python-swifter build fails on 1-core VM #102
Comments
|
Hi @bmwiedemann , Thanks for notifying me, this totally makes sense. In building swifter, I set some high standards for tests to pass. One of those standards requires that If there's anyway to leverage even 2-cores for your test machine, then these should pass. Thanks, |
|
Couldnt you detect the number of CPUs and either skip this kind of test on 1-core machines or lower your requirements? E.g. expect it to be at least half als fast as pandas there. Our build VMs can have variations in performance depending on other builds that happen in other VMs on the same host. |
|
Hey @bmwiedemann, Great idea. I'm currently working on PR #104 to make this change. I will follow-up here when the PR is merged. Thanks for the suggestion, |
|
Follow-up: PR #104 is merged. @bmwiedemann , does openSUSE clone the repo to run the tests or does it require a new release of the package to run them? I want to make sure that your problem is resolved before closing this issue. Thanks, |
|
For openSUSE we usually pull updates in manually and usually use release tarballs. As a coder my main concern would be the large amount of code duplication introduced. But then it is your project and long-term maintenance. |
Originally filed at https://bugzilla.opensuse.org/show_bug.cgi?id=1158578
While working on reproducible builds for openSUSE, I found that
our python-swifter-0.301 package consistently fails some test when building in a 1-core VM
actual results:
The text was updated successfully, but these errors were encountered: