+1 for testing CUDA8 and CUDA9 (i.e. at least one version backward).
I personally had worked recently on functionalities in the linalg-namespace
where I was not aware that I introduced CUDA 8 only dependencies that break
immediately every CUDA7.5 build. I only happened to know this as Jenkins
Good arguments, Marco, Naveen, Pracheer.
+1 to the suggestion of testing CUDA8 in few nightly instances and using
CUDA9 for most instances in CI.
There is no support matrix documented for Apache MXNet and so there is no
forceful upgrade. If a user wants to support a version, they can contribute
Very good points, pracheer.
We have been thinking about running nightly integration tests which will
test the master branch on a wide base of settings (including IoT devices).
How about switching to Cuda 9 in terms of PR validation, and doing
extensive checks on cuda8/9 and another variety of
I agree with Naveen that we shouldn’t be forcing production systems to
forcefully update immediately as soon as the new version comes out. If we want
to get MXNet more adopted, we should think about convenience of the customers
and the pain we might be forcing on them. Having said that, as
I will have to disagree with abandoning a N-1 version of the dependent
libraries as a general guideline for the project. there might be exceptions
to this which should be discussed and agreed on and **well documented** on
the Apache MXNet webpage.
My reasoning is users who are running software in
I like that proposal Bhavin. I'm also interested to see what the other
community members think.
On Sat, Jan 6, 2018 at 6:27 PM, Bhavin Thaker
wrote:
> Hi Kellen,
>
> Here is my opinion and stand on this:
>
> I see no need to test on CUDA8 in Apache MXNet CI, especially
Hi Kellen,
Here is my opinion and stand on this:
I see no need to test on CUDA8 in Apache MXNet CI, especially when CUDA9 is
backward compatible with earlier Nvidia hardware generations. There is time
and resources cost to maintaining the various combinations in the CI and so
I am NOT in favor
Thanks for the thoughts Bhavin, supporting the latest release would also be
an option, and it would be easier from a support point of view.
"2) I think your question probably is what should be tested by the Apache
MXNet CI and NOT what is supported by Apache MXNet, correct?"
I view these two
Hi Kellen,
1) Does Apache MXNet (Incubating) have a support matrix? I think the answer
is no, because I don’t know of where it is documented. One of the mentors
told me earlier that the community uses and modifies the open-source
project as per their individual requirements or those of the