-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Failing backend component tests #11483
Comments
Hi, it seems like you are running backend component tests and not e2e tests. I am to pass the component tests locally, perhaps you can try going to |
My bad! Thanks for clarifying, I'll go check that out and see whats wrong on my side |
I'm getting the same error, did you manage to resolve the issue? |
@NyndoND Hi there just ran it on my computer and I am also getting 5 failing tests. The path for the generated reports has changed slightly since to
![]() From what I recall and what I've seen in this report, its all capitalisation errors for time and might be because of my computers formatting, Mac M1. As long as you make a PR and the component tests passes in the CI, you should be good to go |
E2EBackend Component test fail with exceptionSteps to reproduce
./gradlew componentTest --stackTrace
Expected behaviour
E2E test passes
Actual behaviour
E2E test fails with exception
Additional info
Just wanted to check if this is an actual issue or just on my machine as I saw the PR #11479 passed the E2E CI tests
Edit: Renamed error from E2E to backend component
The text was updated successfully, but these errors were encountered: