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 Failing Dailies #1113

Merged
merged 22 commits into from
Oct 24, 2024
Merged

Fix Failing Dailies #1113

merged 22 commits into from
Oct 24, 2024

Conversation

pauladkisson
Copy link
Member

@pauladkisson pauladkisson commented Oct 14, 2024

Dailies were failing bc os-versions and python-versions were not being propagated properly.

Now fixed -- see here: https://github.com/catalystneuro/neuroconv/actions/runs/11463322663

Daily neuroconv docker tests are failing (see #1121), but since that is a separate problem, we can solve it separately.

@pauladkisson pauladkisson changed the title Fixed Failing Dailies Fix Failing Dailies Oct 15, 2024
Copy link
Collaborator

@h-mayorquin h-mayorquin left a comment

Choose a reason for hiding this comment

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

What do you think about changing the following lines to make the argument non-required for this and the other workflows:

required: true
type: string
default: '["3.9", "3.10", "3.11", "3.12"]'
os-versions:

That way we only need to keep those default versions in one place.

@pauladkisson
Copy link
Member Author

That way we only need to keep those default versions in one place.

Yeah, I think that's a good idea.

@h-mayorquin
Copy link
Collaborator

That way we only need to keep those default versions in one place.

Yeah, I think that's a good idea.

See here for more related discussion:

#1117 (comment)

Tag me when this is ready to take a look.

@pauladkisson
Copy link
Member Author

@h-mayorquin, this is ready to go.

@h-mayorquin
Copy link
Collaborator

Where are you setting vars.ALL_PYTHON_VERSIONS? I would like to have the ability to open a PR when adding support for new versions as I would like to run the testing suit before merging.

@pauladkisson
Copy link
Member Author

Where are you setting vars.ALL_PYTHON_VERSIONS? I would like to have the ability to open a PR when adding support for new versions as I would like to run the testing suit before merging.

It's in the repository variables (right next to secrets)

@h-mayorquin
Copy link
Collaborator

I would prefer to have them in code so we can have a workflow where changing them requires and triggers a PR.

@bendichter bendichter self-requested a review October 22, 2024 17:23
@bendichter
Copy link
Contributor

Oh yeah, that's a good point. Is there a way to put this as a variable in code?

@pauladkisson
Copy link
Member Author

Oh yeah, that's a good point. Is there a way to put this as a variable in code?

As far as I could tell, the only way to include this in the code is to define it separately for each workflow. If we want all the workflows to reference a single variable, I think it has to be a github repository variable: https://github.com/catalystneuro/neuroconv/settings/variables/actions

@h-mayorquin
Copy link
Collaborator

h-mayorquin commented Oct 22, 2024

We can either use the defaults to reduce the duplication (simpler and probably the way to go) or you can write the variable to a file and use bash or an action to read them.

@pauladkisson
Copy link
Member Author

@h-mayorquin how about this solution?

@h-mayorquin
Copy link
Collaborator

Yes, I am glad that the reading from a file option worked. This LGTM.

@h-mayorquin h-mayorquin enabled auto-merge (squash) October 23, 2024 22:51
@h-mayorquin h-mayorquin merged commit 60c5e2a into main Oct 24, 2024
39 of 40 checks passed
@h-mayorquin h-mayorquin deleted the dailies branch October 24, 2024 00:25
Copy link

codecov bot commented Oct 24, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.59%. Comparing base (36464df) to head (5ae0f9f).
Report is 24 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #1113      +/-   ##
==========================================
+ Coverage   90.44%   90.59%   +0.15%     
==========================================
  Files         129      129              
  Lines        8055     8187     +132     
==========================================
+ Hits         7285     7417     +132     
  Misses        770      770              
Flag Coverage Δ
unittests 90.59% <ø> (+0.15%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 2 files with indirect coverage changes

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