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

AssertionError [ERR_ASSERTION]: logs do not look right: 1 #453

Closed
Ark-kun opened this issue Dec 4, 2018 · 2 comments
Closed

AssertionError [ERR_ASSERTION]: logs do not look right: 1 #453

Ark-kun opened this issue Dec 4, 2018 · 2 comments

Comments

@Ark-kun
Copy link
Contributor

Ark-kun commented Dec 4, 2018

https://gubernator.k8s.io/build/kubernetes-jenkins/pr-logs/pull/kubeflow_pipelines/430/presubmit-e2e-test/630/

run-frontend-integration-tests:	․․․․․․Handling connection for 3000
run-frontend-integration-tests:	F22:40:04.744 INFO [ActiveSessions$1.onStop] - Removing session 0fba00219d7e59cb2f76e1d38031312a (org.openqa.selenium.chrome.ChromeDriverService)
run-frontend-integration-tests:	15 passing (34.10s)
run-frontend-integration-tests:	1 failing
run-frontend-integration-tests:	1) deploy helloworld sample run shows logs from node:
run-frontend-integration-tests:	logs do not look right: 1
run-frontend-integration-tests:	running chrome
run-frontend-integration-tests:	AssertionError [ERR_ASSERTION]: logs do not look right: 1
run-frontend-integration-tests:	    at Context.it (/src/helloworld.spec.js:169:5)
run-frontend-integration-tests:	    at new Promise (<anonymous>)
run-frontend-integration-tests:	    at new F (/src/node_modules/core-js/library/modules/_export.js:36:28)
run-frontend-integration-tests:	Wrote xunit report "junit_FrontendIntegrationTestOutput.xml" to [./].
run-frontend-integration-tests:	npm ERR! Test failed.  See above for more details.
@Ark-kun
Copy link
Contributor Author

Ark-kun commented Dec 4, 2018

I'm seeing this flaky error quite often.

@yebrahim
Copy link
Contributor

yebrahim commented Dec 4, 2018

I hope #459 fixes it. Will run it a few times before merging.

Linchin pushed a commit to Linchin/pipelines that referenced this issue Apr 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants