Skip to content

re-add neurostars link #1776

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

Merged
merged 3 commits into from
Jan 20, 2017
Merged

re-add neurostars link #1776

merged 3 commits into from
Jan 20, 2017

Conversation

mgxd
Copy link
Member

@mgxd mgxd commented Jan 10, 2017

No description provided.

@djarecka
Copy link
Collaborator

@mgxd : i've restarted travis to check if the problem would appear again. Travis looks ok now, but I'm not sure if this is problem with travis or with tests... had similar problem 2 weeks ago (but different test): https://travis-ci.org/djarecka/nipype/jobs/189379626

@codecov-io
Copy link

Current coverage is 72.46% (diff: 100%)

Merging #1776 into master will decrease coverage by 0.01%

@@             master      #1776   diff @@
==========================================
  Files          1056       1056          
  Lines         52717      52717          
  Methods           0          0          
  Messages          0          0          
  Branches       7661       7661          
==========================================
- Hits          38211      38204     -7   
- Misses        13296      13302     +6   
- Partials       1210       1211     +1   

Powered by Codecov. Last update 589659d...54b717c

@mgxd
Copy link
Member Author

mgxd commented Jan 20, 2017

@djarecka my early build passed on travis but not circle - although I'm not sure that was due to tests or some docker/conda error

@mgxd mgxd merged commit 7ac0cc7 into master Jan 20, 2017
@mgxd mgxd deleted the fix/readme branch January 20, 2017 15:38
@djarecka
Copy link
Collaborator

@mgxd : your last build only passed travis after I restarted it (not talking about previous problems with CI). Travis doesn't send you emails about broken builds? I'm not able to check this now (or don't know how), but link from emails should still show the previous build that ended with segfault.

@djarecka
Copy link
Collaborator

sorry, probably I shouldn't have restarted but was wondering if it would be OK after restarting, as it was OK in my case 2 weeks ago...

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.

5 participants