mlpack / jenkins-conf Goto Github PK

It seems like most of the sparc64 builds are failing for this reason.

http://masterblaster.mlpack.org/job/mlpack%20-%20nightly%20matrix%20build/arch=sparc64,armadillo=armadillo-7.500.1,buildmode=debug/1463/console
is an example.

In https://github.com/mlpack/jenkins-conf/blob/master/REGISTRY_CONFIG_README.md

I don't think it's masterblaster.

{ ryan@masterblaster }{ /home/jenkins/jobs/mlpack - git commit test/workspace } $ du -h --max-depth=1
964K    ./reports
2.3M    ./test-support
2.6G    ./build
255M    ./repo
2.9G    .

We (or I) should investigate why it takes up so much space. A clue:

{ ryan@masterblaster }{ /home/jenkins/jobs/mlpack - git commit test/workspace/build/bin } $ ls -lh mlpack_knn
-rwxr-xr-x 1 jenkins jenkins 79M Aug 25 16:08 mlpack_knn

79MB! Clearly this is way larger than it should be.

Hello @rcurtin, I am trying to understand the error you described in mlpack/mlpack#1741 and focussed to solve this asap. I have encountered a confusion doubt over the bin folder. It contains executable files to run tests in mlpack if I am correct. Could you please let me know if these executables generated are different for different cases?

Also, let me know that if the jenkins generate only important test cases for each PR depending upon the changes made in specific PR?

@zoq @rcurtin @ShikharJ I am trying to rectify this error asap. Please provide your valuable inputs. Thanks