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

[bug] <sometime e2e test work success, sometime failed> #2293

Closed
tomsun28 opened this issue Jul 17, 2024 · 4 comments · Fixed by #2447
Closed

[bug] <sometime e2e test work success, sometime failed> #2293

tomsun28 opened this issue Jul 17, 2024 · 4 comments · Fixed by #2447
Labels
bug Something isn't working good first issue Good for newcomers question Further information is requested

Comments

@tomsun28
Copy link
Contributor

Question

the e2e test code: https://github.com/apache/hertzbeat/tree/master/e2e

When the code does not involve any changes to e2e, sometimes the e2e test succeeds and sometimes fails, which is very strange.

see action: https://github.com/apache/hertzbeat/actions/workflows/backend-build-test.yml

success: https://github.com/apache/hertzbeat/actions/runs/9957905618

failed: https://github.com/apache/hertzbeat/actions/runs/9957272366

@tomsun28 tomsun28 added good first issue Good for newcomers question Further information is requested bug Something isn't working labels Jul 17, 2024
@yuluo-yx
Copy link
Contributor

yuluo-yx commented Jul 17, 2024

image

image

I looked at the failed actions, and most of the http requests were due to 401 errors, and some were due to container exits

@yuluo-yx
Copy link
Contributor

yuluo-yx commented Jul 17, 2024

btw, 5618 is a failed job, they've reversed the markings. @tomsun28

@tomsun28
Copy link
Contributor Author

I looked at the failed actions, and most of the http requests were due to 401 errors, and some were due to container exits

hi, yes. not sure if the 401 error is caused by not carrying a access token or something else.

@yuluo-yx
Copy link
Contributor

I looked at the failed actions, and most of the http requests were due to 401 errors, and some were due to container exits

hi, yes. not sure if the 401 error is caused by not carrying a access token or something else.

We can keep the running logs inside the container when e2e fails, and then analyze them to get the cause, which requires modifying the e2e test file

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers question Further information is requested
Projects
Development

Successfully merging a pull request may close this issue.

2 participants