verne.freenode.net changed the topic of #mlpack to: http://www.mlpack.org/ -- We don't respond instantly... but we will respond. Give it a few minutes. Or hours. -- Channel logs: http://www.mlpack.org/irc/
sumedhghaisas has quit [Read error: Connection reset by peer]
sumedhghaisas__ has joined #mlpack
sumedhghaisas_ has quit [Read error: Connection reset by peer]
sumedhghaisas__ has quit [Remote host closed the connection]
sumedhghaisas has joined #mlpack
sumedhghaisas has quit [Remote host closed the connection]
sumedhghaisas has joined #mlpack
sumedhghaisas has quit [Read error: Connection reset by peer]
topology has quit [Quit: Page closed]
sumedhghaisas has joined #mlpack
< rcurtin>
zoq: the benchmark commit job is acting strangely... I tried to debug it
< rcurtin>
the console output suggested that the working directory was wrong for cmake, so I tried to print the working directory, and then suddenly cmake was running from the correct directory
< rcurtin>
but then cmake wasn't actually building mlpack, so I modified that and set the options for the build correctly, and now I think it will run correctly...
< rcurtin>
I also added '-j4' to the build options since every benchmark host has 4 cores but only 1 executor, so it's fine to use all 4 cores in one job
< zoq>
hm, I agree that sounds strange. We also have to update the JOB_URL parameter JOB_URL="http://big.mlpack.org.. let me do this right now
< rcurtin>
I tried to do that too but in my browser the editor was behaving very strangely
< rcurtin>
I figured I would try from a different browser another time, but if you have success with it then there is no need for me to play with it anymore :)
< zoq>
I think another reason to switch to another browser, no problem with chrome on my side :)
< rcurtin>
hm, I was actually using chromium here, so maybe the version is old or something
< zoq>
oh, okay
< rcurtin>
I tried using opera on my phone for a while but I ended up giving up on that because it would crash every time I went into a tunnel on the train or something
< rcurtin>
so now I am using chromium there too
< zoq>
looks like the build uses /home/jenkins/workspace/ instead of /home/jenkins/jobs/
< zoq>
the git commit job uses the new path
< rcurtin>
for the benchmark jobs (like the checkout job) I hardcoded the custom workspace path /home/jenkins/workspace since it seemed that the other benchmark jobs also used that
< rcurtin>
if that directory needs to change, it should be easy to do it, but be sure to take a look at the special options for the matrix checkout build, otherwise the workspace will end up in ${workspace_dir}/label/<hostname>/ not just ${workspace_dir}
< zoq>
ah, okay, I think workspace is fine
sumedhghaisas_ has joined #mlpack
sumedhghaisas has quit [Ping timeout: 244 seconds]
sumedhghaisas_ has quit [Ping timeout: 244 seconds]
mentekid has quit [Ping timeout: 244 seconds]
sumedhghaisas_ has joined #mlpack
sumedhghaisas_ has quit [Client Quit]
sumedhghaisas has joined #mlpack
sumedhghaisas has quit [Ping timeout: 244 seconds]