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

Fix CIs #514

Merged
merged 9 commits into from
Feb 24, 2023
Merged

Fix CIs #514

merged 9 commits into from
Feb 24, 2023

Conversation

hmaarrfk
Copy link
Collaborator

@hmaarrfk hmaarrfk commented Oct 22, 2022

I spoke with ukoethe by email and he agreed that dropping python 2.7 would be ok.

Closes: #502

@hmaarrfk
Copy link
Collaborator Author

100% tests passed, 0 tests failed out of 55

@hmaarrfk
Copy link
Collaborator Author

@k-dominik I am trying to keep this to a "CI only change" and I think I'm close.

I'm struggling with windows. If you have a machine handy and want to debug that would be greatly appreciated.

OSX is close, but for some reason i'm getting a segfault. fun!

@k-dominik
Copy link
Collaborator

Hi @hmaarrfk,

awesome effort! I'll look into the windows build tomorrow :)

py38:
PYTHON_VERSION: 3.8
py39:
PYTHON_VERSION: 3.8
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
PYTHON_VERSION: 3.8
PYTHON_VERSION: 3.9

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Thank you. please do not feel offended if i squash this in the end. Part of this exercise is trying to be "careful" in not destroying things.

@k-dominik
Copy link
Collaborator

Hi @hmaarrfk,

is there a reason for the testing strategy with OSX-> py37, linux-> py38, py39, and windows-> py310?

@hmaarrfk
Copy link
Collaborator Author

is there a reason for the testing strategy with OSX-> py37, linux-> py38, py39, and windows-> py310?

Just trying to get a "spread" of python versions without building the full matrix. 3 x 4 -> 12 builds is a little "too much".

@hmaarrfk hmaarrfk closed this Dec 4, 2022
@hmaarrfk hmaarrfk reopened this Dec 4, 2022
@k-dominik k-dominik mentioned this pull request Dec 5, 2022
@hmaarrfk hmaarrfk closed this Feb 19, 2023
@hmaarrfk hmaarrfk reopened this Feb 19, 2023
hmaarrfk and others added 2 commits February 19, 2023 12:55
Co-authored-by: Dominik Kutra <k-dominik@users.noreply.github.com>
build will fail otherwise

would probably better to fix such that also vigranumpy tests are not build
with BUILD_TESTS=OFF
this will indirectly force 14.1 toolset when building, otherwise there is a
standing issue with 14.2 (VS2019).

xref: ref: ukoethe#525
@hmaarrfk
Copy link
Collaborator Author

@k-dominik i'm somewhat tempted to skip OSX and merge this as is. what do you think? There seems to be a few more PRs to modernize the code base that would go through more easily once we have linux + windows CIs in place.

@k-dominik
Copy link
Collaborator

Hello @hmaarrfk,

yes, let's go ahead and merge this. I am always thinking of getting back to vigra and I promise I will ;). Thank you for persisting here!

Cheers
Dominik

@hmaarrfk hmaarrfk merged commit c331366 into ukoethe:master Feb 24, 2023
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.

vigranumpy build error with sphinx 4
2 participants