-
Notifications
You must be signed in to change notification settings - Fork 4
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
Conda env attempt #33
Conversation
…flow things. another workflow yaml gutted from fre-cli for pipeline that lints cylc files and runs data_lineage pytest to start.
…nto workflow file and pytest call for make-timeseries
…s for most. expecting to likely not have all the req deps
…t_conda_env.yml edit). ignore files ending in *tags created by papiex_tooler tests. adjust to some more pythonic conventions inother test scripts
…nce clicking through action logs
currently the workflows are all allowed to succeed on error. i thought it kind for now to give the tests a chance to catch up, but still get the "data" of testing logs going for reference, easy/mindless-feedback, and issue minting. also i think merging wouldn't be allowed with a big red X, so... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @ilaflott ! This is clearly in the right direction, and helpful to @cwhitlock-NOAA whichever way she goes
this isn't supposed to be an all-encompassing conda env for all future fre-workflows functioning. it's more about having a functional-enough pipeline for SOME testing and linting feedback across-the-board.
something is always better than nothing.