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.

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

unit/integration flake: No test results found #25791

Closed
xiangpengzhao opened this issue May 18, 2016 · 6 comments
Closed

unit/integration flake: No test results found #25791

xiangpengzhao opened this issue May 18, 2016 · 6 comments

Comments

@xiangpengzhao
Copy link
Contributor

My PR #25024 failed for Jenkins unit/integration — No test results found. @vishh once helped to trigger the test again, but failure still exists.
#25674 reports a similar problem Jenkins GCE e2e — No test results found.

I also find that several PRs have the same unit/integration flake: #25737, #25771, etc.

@lavalamp would you please help to check this? Thanks!

The build-log is shown as below:

https://console.cloud.google.com/m/cloudstorage/b/kubernetes-jenkins/o/pr-logs/pull/25024/kubernetes-pull-test-unit-integration/25017/build-log.txt

+++ [0509 13:06:26] Placing binaries
SUCCESS  ./hack/../hack/verify-symbols.sh   38s
Verifying ./hack/../hack/verify-flags-underscore.py
SUCCESS  ./hack/../hack/verify-flags-underscore.py  28s
Build step 'Execute shell' marked build as failure
Recording test results
ERROR: Step 鈥楶ublish JUnit test result report鈥� failed: No test report files were found. Configuration error?
[PostBuildScript] - Execution post build scripts.
[kubernetes-pull-test-unit-integration@2] $ /bin/bash -xe /tmp/hudson5373222481076070063.sh
+ [[ -x ./hack/jenkins/upload-to-gcs.sh ]]
+ ./hack/jenkins/upload-to-gcs.sh
Called without JENKINS_BUILD_STARTED or JENKINS_BUILD_FINISHED set.
Assuming a legacy invocation.
Run finished at Mon May  9 13:06:58 PDT 2016
Uploading to gs://kubernetes-jenkins/pr-logs/pull/25024/kubernetes-pull-test-unit-integration/25017 (attempt 1)
Uploading build result: [UNSET]
Marking build 25017 as the latest completed build
@xiangpengzhao
Copy link
Contributor Author

The build log also shows

Verifying ./hack/../hack/verify-gofmt.sh
!!! 'gofmt -s' needs to be run on the following files: 
./pkg/kubelet/dockertools/docker.go
FAILED   ./hack/../hack/verify-gofmt.sh 8s

But it seems that there is no format problem in the file.

@lavalamp
Copy link
Member

Looks like you found the problem. Please make sure you're running gofmt with -s option and use the same version that the server is using, should be 1.6 now?

@xiangpengzhao
Copy link
Contributor Author

I build Kubernetes using Docker (instructions). I think the containerized build env version is the same with that the server is using. Will the unit/integration test be blocked if verify-gofmt.sh returns FAILED?
Thanks! @lavalamp

@lavalamp
Copy link
Member

Yes, verify-gofmt.sh must succeed.

@xiangpengzhao
Copy link
Contributor Author

Thanks 😄

@xiangpengzhao
Copy link
Contributor Author

The Jenkins unit/integration of PR #25024 shows 6142 tests run, 24 skipped, 0 failed. now, but its status is failed.

PTAL @lavalamp , thanks!

build-log.txt

Some error messages:

................
FAIL!
Get deployment {{range.items}}{{.spec.paused}}:{{end}}
  Expected: true:true:
  Got:      <no value>:true:
�(B
1091 ./hack/test-cmd.sh
�(B
!!! Error in ./hack/test-cmd.sh:53
  'return 1' exited with status 1
Call stack:
  1: ./hack/test-cmd.sh:53 runTests(...)
  2: ./hack/test-cmd.sh:2176 main(...)
Exiting with status 1
+++ [0520 10:38:25] Clean up complete
Build step 'Execute shell' marked build as failure
Recording test results

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants