Re: CI system seems to be using python3 for python2 builds

Thanks for your sharing information. > 1. Looks like this backtrace has been present since long time, since this > was not a test failure or build failure we never got notified about it. Here > >

Re: CI system seems to be using python3 for python2 builds

Hi Gautam, I see that ‘nosetests’ is the command used to run python2 tests. It looks like that’s being mapped to use python3. I’ve checked that this is the case on my Ubuntu instance. I need to use ‘nosetests-2.7’ to use python2 for the tests. Please check if this fix works in the build

Re: CI system seems to be using python3 for python2 builds

Hi Ozawa, Thanks for follow up. Unfortunately I didn't get time to work on this today. However I have couple of points to mentions. 1. Looks like this backtrace has been present since long time, since this was not a test failure or build failure we never got notified about it. Here

Re: CI system seems to be using python3 for python2 builds

Hi Kumar, Thanks for looking into the issue. How is the progress of this problem? Shouldn't we call /usr/bin/env python2 or python2.7 in following source code instead of python since MXNet only supports python2 currently? I think default version of python in Ubuntu is now python3, so it can cause

Re: CI system seems to be using python3 for python2 builds

Many thanks Gautam. On 9/26/17, 8:37 PM, "Kumar, Gautam" wrote: Hi Kellen, This issue has been happening since last 3-4 days along with few other test failure. I am looking into it. -Gautam On 9/26/17, 7:45 AM, "Sunderland, Kellen"

Re: CI system seems to be using python3 for python2 builds

Hi Kellen, This issue has been happening since last 3-4 days along with few other test failure. I am looking into it. -Gautam On 9/26/17, 7:45 AM, "Sunderland, Kellen" wrote: I’ve been noticing in a few failed builds that the stack trace indicates we’re