1

I'm using R scripts with C++ code under the hood. An error message references a Jenkins Workspace with the file I'd like to debug. The workspace directory appears to be temporary and I'm unable to find this file:

c:\jenkins\workspace\mxnet\mxnet\src\operator\tensor../elemwise_op_common.h:123: Check failed: assign(&dattr, (*vec)[i])

How should the directory c:\jenkins\workspace\... be understood?

Where would I look for the header file elemwise_op_common.h?

alex
  • 5,636
  • 9
  • 47
  • 97
Conner M.
  • 1,785
  • 3
  • 17
  • 28

1 Answers1

0

The file should be in 

 c:\jenkins\workspace\mxnet\mxnet\src\operator\elemwise_op_common.h

The \../ being for getting one folder up.

The workspace is where Jenkins checks out the sources, and execute its job.
It differs from a build.
See more at "Building a software project".

VonC
  • 1,129,465
  • 480
  • 4,036
  • 4,755
  • Is `/jenkins/` a temporary or invisible file? I don't see it under `c:/`. – Conner M. Nov 18 '18 at 03:28
  • 1
    @ConnerM. No it is the folder used by the *agent*. In a simple installation, the machine hosting the Jenkins server also acts as an agent. But in your case, if you have a separate machine for that agent, then C:\jenkins would be there. – VonC Nov 18 '18 at 03:30
  • @ConnerM. As for the header itself... maybe https://github.com/apache/incubator-mxnet/blob/master/src/operator/elemwise_op_common.h. – VonC Nov 18 '18 at 03:31
  • https://wiki.jenkins.io/display/JENKINS/Building+a+software+project does not explain what a workspace is. – alex Dec 02 '19 at 19:10
  • @alex True, and it depends if you are using pipelines or not (https://www.selikoff.net/2016/07/10/workspace-jenkins-pipelines/. If not, https://wiki.jenkins.io/display/JENKINS/Administering+Jenkins – VonC Dec 02 '19 at 20:01