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

where would it make sense to test running an analysis? #113

Open
jdkent opened this issue Oct 20, 2020 · 3 comments
Open

where would it make sense to test running an analysis? #113

jdkent opened this issue Oct 20, 2020 · 3 comments

Comments

@jdkent
Copy link

jdkent commented Oct 20, 2020

Since I ran into an unexpected error after updating, would it make sense to place a test in this repo for running a little analysis in continuous integration?
Or would there be a better place? Or is a test not needed?

@adelavega
Copy link
Contributor

yeah that wouldn't be a bad idea. fitlins should also have more robust tests than it currently does.

possible we could set up Circle CI, and using pyns create an analysis in neuroscout which is then run (so the whole pipeline is "fresh"). I think as long as this isn't getting triggered all the time, it would be a good test to run periodically.

@adelavega
Copy link
Contributor

if you have any expertise with that, and want to help lmk

@adelavega
Copy link
Contributor

also, just pinning a "stable" version will also help, but definitely testing makes sense, just haven't gotten around to it.

@adelavega adelavega reopened this Jul 21, 2021
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

No branches or pull requests

2 participants