Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

e2e flake: no longer a configured node #27214

Closed
euank opened this issue Jun 10, 2016 · 6 comments
Closed

e2e flake: no longer a configured node #27214

euank opened this issue Jun 10, 2016 · 6 comments
Labels
area/test-infra lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/testing Categorizes an issue or PR as relevant to SIG Testing.

Comments

@euank
Copy link
Contributor

euank commented Jun 10, 2016

The internal link is: http://goto.google.com/prkubekins/job/kubernetes-pull-build-test-e2e-gce//44196

The other "not found" link is https://console.cloud.google.com/storage/browser/kubernetes-jenkins/pr-logs/pull/26759/kubernetes-pull-build-test-e2e-gce/44196/

Hopefully the internal link has some information, I can't view it to check.
@euank euank mentioned this issue Jun 10, 2016
Closed
@euank
Copy link
Contributor Author

euank commented Jun 10, 2016

Another occurrence: #27208, internal link http://goto.google.com/prkubekins/job/kubernetes-pull-build-test-e2e-gce//44198

@Random-Liu Random-Liu mentioned this issue Jun 13, 2016
Merged
@lavalamp
Copy link
Member

actual error is:

FATAL: no longer a configured node for agent-pr-1
java.lang.IllegalStateException: no longer a configured node for agent-pr-1
    at hudson.model.AbstractBuild$AbstractBuildExecution.getCurrentNode(AbstractBuild.java:453)
    at hudson.model.AbstractBuild$AbstractBuildExecution.reportBrokenChannel(AbstractBuild.java:810)
    at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785)
    at hudson.model.Build$BuildExecution.build(Build.java:205)
    at hudson.model.Build$BuildExecution.doRun(Build.java:162)
    at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
    at hudson.model.Run.execute(Run.java:1738)
    at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
    at hudson.model.ResourceController.execute(ResourceController.java:98)
    at hudson.model.Executor.run(Executor.java:410)
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for kubernetes-pull-build-test-e2e-gce #44196
[PostBuildScript] - Execution post build scripts.
ERROR: Build step failed with exception
java.lang.NullPointerException: no such build node: agent-pr-1
    at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:72)
    at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:64)
    at org.jenkinsci.plugins.postbuildscript.PostBuildScript.processBuildSteps(PostBuildScript.java:204)
    at org.jenkinsci.plugins.postbuildscript.PostBuildScript.processScripts(PostBuildScript.java:143)
    at org.jenkinsci.plugins.postbuildscript.PostBuildScript._perform(PostBuildScript.java:105)
    at org.jenkinsci.plugins.postbuildscript.PostBuildScript.perform(PostBuildScript.java:85)
    at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
    at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782)
    at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723)
    at hudson.model.Build$BuildExecution.post2(Build.java:185)
    at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:668)
    at hudson.model.Run.execute(Run.java:1763)
    at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
    at hudson.model.ResourceController.execute(ResourceController.java:98)
    at hudson.model.Executor.run(Executor.java:410)
Build step 'Execute a set of scripts' marked build as failure
ERROR: Build step failed with exception
java.lang.NullPointerException
    at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:187)
    at com.google.jenkins.plugins.storage.AbstractUpload.perform(AbstractUpload.java:176)
    at com.google.jenkins.plugins.storage.GoogleCloudStorageUploader.perform(GoogleCloudStorageUploader.java:109)
    at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
    at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782)
    at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723)
    at hudson.model.Build$BuildExecution.post2(Build.java:185)
    at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:668)
    at hudson.model.Run.execute(Run.java:1763)
    at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
    at hudson.model.ResourceController.execute(ResourceController.java:98)
    at hudson.model.Executor.run(Executor.java:410)
Build step 'Google Cloud Storage Uploader' marked build as failure
ERROR: Step ‘Set build status on GitHub commit [deprecated]’ failed: no workspace for kubernetes-pull-build-test-e2e-gce #44196
Setting status of 098b9f0603f820ee04d11ba61146425219cb6e91 to FAILURE with url https://console.cloud.google.com/storage/browser/kubernetes-jenkins/pr-logs/pull/26759/kubernetes-pull-build-test-e2e-gce/44196/ and message: ' No test results found.'
Using context: Jenkins GCE e2e

@lavalamp lavalamp changed the title e2e flake: No test results found e2e flake: no longer a configured node Jun 15, 2016
@k8s-github-robot k8s-github-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label May 31, 2017
@0xmichalis
Copy link
Contributor

/sig testing

@k8s-ci-robot k8s-ci-robot added the sig/testing Categorizes an issue or PR as relevant to SIG Testing. label Jun 22, 2017
@k8s-github-robot k8s-github-robot removed the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Jun 23, 2017
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 29, 2017
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 28, 2018
@euank
Copy link
Contributor Author

euank commented Feb 7, 2018

Closing as stale
/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/test-infra lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/testing Categorizes an issue or PR as relevant to SIG Testing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@lavalamp @euank @0xmichalis @k8s-github-robot @k8s-ci-robot @fejta-bot