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

Warnings removals and python 3.9 drop in tests #2860

Merged
merged 10 commits into from
Apr 26, 2024

Conversation

wpotrzebowski
Copy link
Contributor

@wpotrzebowski wpotrzebowski commented Apr 21, 2024

Description

It is now down to one warning, which cannot easily be fixed due to dependent action.

Removing warnings created by GH actions and dropping support for python 3.9 in tests (as it seems to be not available on latest-macos runners actions/setup-python#850)

@rozyczko
Copy link
Member

Just a note: how is this PR different from @butlerpd 's #2836 ?

@wpotrzebowski
Copy link
Contributor Author

Ah, I thought I saw it somewhere already... @rozyczko Thanks for point it out. I will merge/move to #2836

@wpotrzebowski wpotrzebowski changed the title Warnings removal Warnings removals and python 3.9 drop Apr 24, 2024
@wpotrzebowski wpotrzebowski changed the title Warnings removals and python 3.9 drop Warnings removals and python 3.9 drop in tests Apr 24, 2024
@wpotrzebowski wpotrzebowski marked this pull request as ready for review April 24, 2024 19:59
Copy link
Member

@rozyczko rozyczko left a comment

Choose a reason for hiding this comment

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

Looks good. Works as expected.
One minor issue raised which does not block merging.

with:
name: SasView-Installer-${{ matrix.os }}-${{ matrix.python-version }}
path: |
installers/dist/setupSasView.exe
installers/dist/SasView6.dmg
installers/dist/sasview6.tar.gz
if-no-files-found: error
if-no-files-found: ignore
Copy link
Member

Choose a reason for hiding this comment

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

Is this a good idea? Shouldn't the build be marked failed if the installer is not present?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, the problem with this one is that action only sees the current OS installer (e.g. Windows runner doesn't produce OSX installer). If one want to do it properly, we will probably have to split it into 3 actions and I considered doing that. However, the "error" only seems to throw the warning and it still proceeds the build. Therefore "ignoring" seems to be pragmatic solution here...

@krzywon krzywon merged commit e4912da into release_6.0.0 Apr 26, 2024
28 checks passed
@krzywon krzywon deleted the remove_warnings_from_gh_summary branch April 26, 2024 11:54
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.

3 participants