shaneknapp commented on issue #23514: [SPARK-24902][K8s] Add PV integration 
tests
URL: https://github.com/apache/spark/pull/23514#issuecomment-461972613
 
 
   > @shaneknapp
   > 
   > > `chowning` /tmp to be owned by jenkins seem reasonable for this one 
test. :\
   > 
   > Can we make a convention like /tmp/k8s-tests or /k8s-tests so I can use 
that and let jenkins user own it?
   > Then I can just use that convention all the way in the container?
   
   ok...   more testing results are in.  progress was made:
   
   - i hacked `PVTestsSuite.scala` and set `val HOST_PATH` to point to a 
jenkins-owned directory named `/tmp/tmp.TiXnVGc4Vv`
   - dist built
   - integration tests run with the following instantiation of `minikube`:  
`minikube --vm-driver=kvm2 start --memory 6000 --cpus 8 
--mount-string="/tmp/tmp.TiXnVGc4Vv:/tmp/tmp.TiXnVGc4Vv" --mount`
   - when we hit the PV integration tests the following happened:
     - the tmp file was created successfully in the jenkins-owned dir i set in 
`PVTestsSuite.scala` with the contents of `test PVs`
     - the executor containers created, and ran, but errored out before i could 
grab logs. 
     - after two minutes, the build dumped out a big stack trace.
   - the errors all seem to point to this:  `java.io.IOException: Mkdirs failed 
to create 
file:/opt/spark/pv-tests/dfs_read_write_test/_temporary/0/_temporary/attempt_20190208213300_0001_m_000000_0
 (exists=false, cwd=file:/opt/spark/work-dir)`
   
   i've also attached the pertinent logs to this comment.
   
   i don't have any more time today to spend debugging this, but i'll have some 
time this weekend and next week.
   
[build-stacktrace.log](https://github.com/apache/spark/files/2847165/build-stacktrace.log)
   
[kubectl-describe-pod.log](https://github.com/apache/spark/files/2847166/kubectl-describe-pod.log)
   
[kubectl-events.log](https://github.com/apache/spark/files/2847167/kubectl-events.log)
   
[kubectl-log.log](https://github.com/apache/spark/files/2847168/kubectl-log.log)
   
   
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to