yeah, it could be completely unrelated to the build env, but it's late and i'm not going to dive in to this tonite. :)
On Mon, Sep 16, 2019 at 9:13 PM Jungtaek Lim <kabh...@gmail.com> wrote: > > Thanks for following up and providing the info! I'll also keep an eye after > clean-up to see whether it helps. > > On Tue, Sep 17, 2019 at 1:08 PM Shane Knapp <skn...@berkeley.edu> wrote: >> >> > Note that they're different workers (amp-jenkins-worker-0x) with same >> > workspace /home/jenkins/workspace/SparkPullRequestBuilder@6. >> > >> the '@6' refers to the executor number that the build ran on (look at >> the jenkins ui and the numbers next to each slot for each worker). >> >> oddly, at the beginning of the build when we overload HOME to point to >> the .ivy dir, the executor doesn't seem to match up with what >> per-executor dir is being set to. example: >> >> https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/110688/consoleFull >> executor number is 8 (from >> https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/110688/injectedEnvVars) >> HOME is set properly: + HOME=/home/sparkivy/per-executor-caches/8 >> but the dir the build runs from is indeed >> /home/jenkins/workspace/SparkPullRequestBuilder@6/ >> >> > Any guess/suspect? >> > >> nope. no clue whatsoever. ¯\_(ツ)_/¯ >> >> what i CAN do first thing tomorrow is pause builds, wipe out the >> ivy/sbt caches and SparkPullRequestBuilder* dirs on all workers and >> see if that helps. >> >> shane >> -- >> Shane Knapp >> UC Berkeley EECS Research / RISELab Staff Technical Lead >> https://rise.cs.berkeley.edu > > > > -- > Name : Jungtaek Lim > Blog : http://medium.com/@heartsavior > Twitter : http://twitter.com/heartsavior > LinkedIn : http://www.linkedin.com/in/heartsavior -- Shane Knapp UC Berkeley EECS Research / RISELab Staff Technical Lead https://rise.cs.berkeley.edu --------------------------------------------------------------------- To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
