Closed Garyfallidis closed 8 years ago
Same issue now on Python 3.3 http://nipy.bic.berkeley.edu/builders/dipy-bdist32-33/builds/208
It looks like you're trying to run a try_branch.py
run from the wrong repository, or where the repository is on a branch that is massively out of date. Is that possible?
Specifically it looks like you're trying to run try_branch.py
from the nibabel repository.
I am definitely not doing that personally. But maybe some of the other devs is doing so. @omarocegueda, @arokem, @marccote... Is it you guys?
I'm currently not using try_branch. I'm trying to reproduce the Appveyor reported failure on a virtual machine... no luck so far =(
It's not me. @omarcegueda: thanks for putting the time in that. It's a real annoying one - it seems intermittent too. For example, it passed just 3 days ago, when I rebased that branch: https://ci.appveyor.com/project/arokem/dipy/build/1.0.584
On Thu, Jan 14, 2016 at 11:58 AM, Omar Ocegueda notifications@github.com wrote:
I'm currently not using try_branch. I'm trying to reproduce the Appveyor reported failure on a virtual machine... no luck so far =(
— Reply to this email directly or view it on GitHub https://github.com/nipy/nibotmi/issues/25#issuecomment-171762856.
If y'all need to log into any of the buildbots directly, let me know.
Sorry guys, it was probably me. Yesterday, Matthew gave me access to the buildbot so I could debug a MemoryError of my nibabel's PR. I wasn't sure how to use try_branch.py and just pasted what Matthew sent me by email for the name of the bot. It tried to run a Nibabel patch on dipy-bdist32-27 !
Edit: However, it only happened once yesterday. Edit2: I have nothing to do with the error on dipy-bdist32-33 though.
Oops - my fault for sending the wrong builder name...
dipy-bdist32-33 error is something unrelated, not sure what caused it, I deleted the relevant directory and just reran the build: http://nipy.bic.berkeley.edu/builders/dipy-bdist32-33/builds/210
Meanwhile original buildbot has rerun its nightly build without error : http://nipy.bic.berkeley.edu/builders/dipy-bdist32-27/builds/303
So I think this issue can be closed.
http://nipy.bic.berkeley.edu/builders/dipy-bdist32-27/builds/301
STDIO output using PTY: False