On Mon, 8 May 2017 12:27:55 +0200 Ward Poelmans <[email protected]> wrote:
> OK, they did something I didn't expect. Apparently commit 0d64855f741e04 > for nnvm was also added to mxnet itself. This makes that EB downloads > the wrong tarball... > > I've changed the commit I use of nnvm for now. I will look into the > framework so we can specify from which url which tarball should be > downloaded. This now works fine. I've build mxnet from eb 3.3.0 for nehalem and sandybridge and sanity checks are passing, yay! :) Just haswell remaining ... and boom. Sanity check for python fails with: == 2017-06-27 11:05:27,003 extension.py:181 WARNING Extension: MXNet failed to install, cmd '/g/easybuild/x86_64/CentOS/7/haswell/software/Python/2.7.12-foss-2016b/bin/python -c "import mxnet"' (stdin: None) output: terminate called after throwing an instance of 'std::system_error' what(): Operation not permitted Which is something I'm seeing for the first time. Google tells me that is is somehow related to -pthread or a bug in the code itself. Both seems unlikely since builds for different architectures passed. Any hint how to figure out this one? -- Jurij Pečar HPC Engineer, IT Operations, IT Services EMBL Heidelberg, Meyerhofstraße 1, 69117, Heidelberg, Germany Room 13-401
