the AmplabJenks bot's github creds are out of date, which is causing that non-fatal error.  however, if you scroll back you'll see that minikube actually failed to start.  that should have definitely failed the build, so i'll look at the job's bash logic and see what we missed.

also, that worker (research-jenkins-worker-07) had some lingering builds running and i bet there was a collision w/a dangling minikube instance.  i'm rebooting that worker now.


On Tue, Feb 23, 2021 at 6:47 AM Sean Owen <> wrote:
Shane would you know? May be a problem with a single worker.

On Tue, Feb 23, 2021 at 8:46 AM Phillip Henry <> wrote:


Silly question: the Jenkins build for my PR is failing but it seems outside of my control. What must I do to remedy this?

I've submitted

but Spark QA is telling me "Kubernetes integration test status failure".

The Jenkins job says "SUCCESS" but also barfs with:

FileNotFoundException means that the credentials Jenkins is using is probably wrong. Or the user account does not have write access to the repo.

Can anybody please advise?

Thanks in advance.


Shane Knapp
Computer Guy / Voice of Reason
UC Berkeley EECS Research / RISELab Staff Technical Lead