GitHub user ZeroWiggliness created a discussion: Flaky Frontend Tests?
Hi,
I wasn't sure where to ask or if I should open a bug. Are the tests flaky? We
get a lot of test timeouts and we see similar sometimes in the failed actions.
We are struggling to get all the tests to pass because of numerous timeouts.
Some of these tests we see also failed in the actions here in the repo.
We have tried npm run tests and also similar to the github build machines with:
`
docker` buildx build -t test01042026
--cache-from=type=registry,ref=apache/superset-cache:3.10-slim-bookworm
--target superset-node-ci .
mkdir -p superset-frontend/coverage
docker run -v ./superset-frontend/coverage:/app/superset-frontend/coverage --rm
test01042026:latest bash -c "npm run test -- --coverage
--coverageReporters=json-summary"
`
and we get very similar issues but not always the same. Sometimes they all pass
if we use sharding but not always, without we always get failures.
For reference we are using the 6.0 branch.
Example:
FAIL src/dashboard/components/EmbeddedModal/EmbeddedModal.test.tsx (101.488 s)
● enables embedding
thrown: "Exceeded timeout of 20000 ms for a test.
Add a timeout value to this test to increase the timeout, if this is a
long-running test. See https://jestjs.io/docs/api#testname-fn-timeout.";
105 | });
106 |
> 107 | test('enables embedding', async () => {
| ^
108 | setMockApiNotFound();
109 | setup();
110 |
at Object.test
(src/dashboard/components/EmbeddedModal/EmbeddedModal.test.tsx:107:1)
Any solution for this would be great.
GitHub link: https://github.com/apache/superset/discussions/39010
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
