Update

.github/workflows/test_multiple_arch.yaml

@@ -33,7 +33,6 @@ jobs:
       - uses: actions/checkout@v2
       - uses: ./.github/actions/download-dl4j-test-resources-linux
       - uses: ./.github/actions/install-protobuf-linux
-      - uses: ./.github/actions/install-cmake-linux
       - uses: uraimo/run-on-arch-action@v2.0.8
         name: Build and test with ${{ matrix.arch }} ${{ matrix.distro }}
         id: build
@@ -53,6 +52,9 @@ jobs:
                echo "After install on architecture ${{ matrix.arch }}"
                mkdir -p "/opt/maven"
                curl -fsSL http://apache.osuosl.org/maven/maven-3/3.6.3/binaries/apache-maven-3.6.3-bin.tar.gz | tar -xzC "/opt/maven" --strip-components=1
+               apt-get -yq  update && apt-get install -y build-essential unzip libssl-dev
+               curl -fsSL http://cmake.org/files/v3.19/cmake-3.19.0.tar.gz | tar xz && cd cmake-3.19.0
+                                 ./configure --prefix=/opt/cmake && make -j2 && make install && cd .. && rm -r cmake-3.19.0
                export PATH="/opt/maven/bin:$PATH"
                    echo "RUNNING ARCH ${{ matrix.arch }}"
                             case "${{ matrix.arch }}" in
@@ -69,8 +71,21 @@ jobs:
                   mvn --version
                   export PATH="/opt/cmake/bin:/opt/maven/bin:/opt/protobuf/bin:$PATH"
                   cmake --version
+                  wget https://github.com/KonduitAI/dl4j-test-resources/archive/master.zip && unzip master.zip
+                  cd dl4j-test-resources-master
+                  mvn clean install -DskipTests
+                  echo "Extracted test resources"
                   echo "Running build in ${pwd}"
-                   mvn  -X -Possrh -pl :nd4j-tests  -Djavacpp.platform=linux-x86_64 -Dlibnd4j.chip=cpu -Pcpu --batch-mode clean test -Dtest=org.nd4j.smoketests.SmokeTest
+                  curl -fsSL https://github.com/google/protobuf/releases/download/v3.5.1/protobuf-cpp-3.5.1.tar.gz \
+                                       | tar xz && \
+                                       cd protobuf-3.5.1 && \
+                                       ./configure --prefix=/opt/protobuf && \
+                                       make -j2 && \
+                                       make install && \
+                                       cd .. && \
+                                       rm -rf protobuf-3.5.1
+                  echo "/opt/protobuf/bin" >> $GITHUB_PATH
+                  mvn  -X -Possrh -pl :nd4j-tests  -Djavacpp.platform=linux-${{matrix.arch}} -Dlibnd4j.chip=cpu -Pcpu --batch-mode clean test -Dtest=org.nd4j.smoketests.SmokeTest
 
 
 

libnd4j/buildnativeoperations.sh

@@ -438,9 +438,9 @@ fi
 
 if [ -z "$COMPUTE" ]; then
   if [ "$ARCH" == "x86-64" ]; then
-   COMPUTE="5.0 5.2 5.3 6.0 6.2 8.0"
+   COMPUTE="5.0 5.2 5.3 6.0 8.0"
   else
-      COMPUTE="5.0 5.2 5.3 6.0 6.2"
+      COMPUTE="5.0 5.2 5.3 6.0"
   fi
 fi
 

nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/ir/TensorNamespace.java

@@ -5411,14 +5411,12 @@ public final class TensorNamespace {
      * Serializations can either use one of the fields above, or use this
      * raw bytes field. The only exception is the string case, where one is
      * required to store the content in the repeated bytes string_data field.
-     *
      * When this raw_data field is used to store tensor value, elements MUST
      * be stored in as fixed-width, little-endian order.
      * Floating-point data types MUST be stored in IEEE 754 format.
      * Complex64 elements must be written as two consecutive FLOAT values, real component first.
      * Complex128 elements must be written as two consecutive DOUBLE values, real component first.
      * Boolean type MUST be written one byte per tensor element (00000001 for true, 00000000 for false).
-     *
      * Note: the advantage of specific field rather than the raw_data field is
      * that in some cases (e.g. int data), protobuf does a better packing via
      * variable length storage, and may lead to smaller binary footprint.
@@ -5657,7 +5655,6 @@ public final class TensorNamespace {
   /**
    * <pre>
    * Tensors
-   *
    * A serialized tensor value.
    * </pre>
    *
@@ -7013,14 +7010,12 @@ public final class TensorNamespace {
      * Serializations can either use one of the fields above, or use this
      * raw bytes field. The only exception is the string case, where one is
      * required to store the content in the repeated bytes string_data field.
-     *
      * When this raw_data field is used to store tensor value, elements MUST
      * be stored in as fixed-width, little-endian order.
      * Floating-point data types MUST be stored in IEEE 754 format.
      * Complex64 elements must be written as two consecutive FLOAT values, real component first.
      * Complex128 elements must be written as two consecutive DOUBLE values, real component first.
      * Boolean type MUST be written one byte per tensor element (00000001 for true, 00000000 for false).
-     *
      * Note: the advantage of specific field rather than the raw_data field is
      * that in some cases (e.g. int data), protobuf does a better packing via
      * variable length storage, and may lead to smaller binary footprint.
@@ -7771,7 +7766,6 @@ public final class TensorNamespace {
     /**
      * <pre>
      * Tensors
-     *
      * A serialized tensor value.
      * </pre>
      *
@@ -9086,14 +9080,12 @@ public final class TensorNamespace {
        * Serializations can either use one of the fields above, or use this
        * raw bytes field. The only exception is the string case, where one is
        * required to store the content in the repeated bytes string_data field.
-       *
        * When this raw_data field is used to store tensor value, elements MUST
        * be stored in as fixed-width, little-endian order.
        * Floating-point data types MUST be stored in IEEE 754 format.
        * Complex64 elements must be written as two consecutive FLOAT values, real component first.
        * Complex128 elements must be written as two consecutive DOUBLE values, real component first.
        * Boolean type MUST be written one byte per tensor element (00000001 for true, 00000000 for false).
-       *
        * Note: the advantage of specific field rather than the raw_data field is
        * that in some cases (e.g. int data), protobuf does a better packing via
        * variable length storage, and may lead to smaller binary footprint.
@@ -9110,14 +9102,12 @@ public final class TensorNamespace {
        * Serializations can either use one of the fields above, or use this
        * raw bytes field. The only exception is the string case, where one is
        * required to store the content in the repeated bytes string_data field.
-       *
        * When this raw_data field is used to store tensor value, elements MUST
        * be stored in as fixed-width, little-endian order.
        * Floating-point data types MUST be stored in IEEE 754 format.
        * Complex64 elements must be written as two consecutive FLOAT values, real component first.
        * Complex128 elements must be written as two consecutive DOUBLE values, real component first.
        * Boolean type MUST be written one byte per tensor element (00000001 for true, 00000000 for false).
-       *
        * Note: the advantage of specific field rather than the raw_data field is
        * that in some cases (e.g. int data), protobuf does a better packing via
        * variable length storage, and may lead to smaller binary footprint.
@@ -9140,14 +9130,12 @@ public final class TensorNamespace {
        * Serializations can either use one of the fields above, or use this
        * raw bytes field. The only exception is the string case, where one is
        * required to store the content in the repeated bytes string_data field.
-       *
        * When this raw_data field is used to store tensor value, elements MUST
        * be stored in as fixed-width, little-endian order.
        * Floating-point data types MUST be stored in IEEE 754 format.
        * Complex64 elements must be written as two consecutive FLOAT values, real component first.
        * Complex128 elements must be written as two consecutive DOUBLE values, real component first.
        * Boolean type MUST be written one byte per tensor element (00000001 for true, 00000000 for false).
-       *
        * Note: the advantage of specific field rather than the raw_data field is
        * that in some cases (e.g. int data), protobuf does a better packing via
        * variable length storage, and may lead to smaller binary footprint.