Skip to content

e2e pool-load-success test hanging on close #3063

@philrz

Description

@philrz

Repro is with Zui commit ca047c0.

When working with Zui since the merge of #3061, I noticed one of the e2e tests failing that hadn't been before. How the failure looks:

  ✘  2 pool-load-success.spec.ts:27:7 › Pool Loads (successes) › load more data into the pool (2.5s)
  1) pool-load-success.spec.ts:27:7 › Pool Loads (successes) › load more data into the pool ────────
    "afterAll" hook timeout of 30000ms exceeded.
      10 |   });
      11 |
    > 12 |   test.afterAll(async () => {
         |        ^
      13 |     await app.shutdown();
      14 |   });
      15 |
        at /Users/phil/work/zui/packages/zui-player/tests/pool-load-success.spec.ts:12:8
  1 failed
    pool-load-success.spec.ts:27:7 › Pool Loads (successes) › load more data into the pool ─────────

I just did a controlled set of repros and it does indeed seem like the failures are correlated with those changes. I used these repro steps:

$ SUCCESSES=0; FAILURES=0; while true; do   yarn e2e -g pool-load-success.spec.ts --skip-nx-cache; if [ $? -eq 0 ] ; then SUCCESSES=$(expr $SUCCESSES + 1); else FAILURES=$(expr $FAILURES + 1); fi; echo "Successful test runs=$SUCCESSES, failed test runs=$FAILURES"; done

Running at commit 59c4c4a that was right before the changes in #3061 produced 53 successful runs and 0 failures before I stopped it. At commit ca047c0 for the merge of #3061 it produced 46 successful runs and 10 failures.

Metadata

Metadata

Assignees

Labels

testCreating/improving test automation

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions