fix #115
GitHub Actions / Test results: E2E (linux) 3th node
succeeded
Dec 20, 2024 in 0s
30 passed, 1 failed and 0 skipped
❌ tests/e2e/mochawesome-report/junit-report.xml
31 tests were completed in 627s with 30 passed, 1 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| Filtering per key name in DB with 10 millions of keys | 1✅ | 1❌ | 154s |
❌ Filtering per key name in DB with 10 millions of keys
Verify that user can filter per exact key without using any patterns in DB with 10 millions of keys
✅ Filtering per key name in DB with 10 millions of keys Verify that user can filter per exact key without using any patterns in DB with 10 millions of keys
Verify that user can filter per key name using patterns in DB with 10-50 millions of keys
❌ Filtering per key name in DB with 10 millions of keys Verify that user can filter per key name using patterns in DB with 10-50 millions of keys
AssertionError: Keys filtered incorrectly by key type after scanning more: expected 'device_eu-central-1_31_zset' to include 'hash'
Annotations
Check failure on line 0 in tests/e2e/mochawesome-report/junit-report.xml
github-actions / Test results: E2E (linux) 3th node
Filtering per key name in DB with 10 millions of keys ► Verify that user can filter per key name using patterns in DB with 10-50 millions of keys ► Filtering per key name in DB with 10 millions of keys Verify that user can filter per key name using pat...
Failed test found in:
tests/e2e/mochawesome-report/junit-report.xml
Error:
AssertionError: Keys filtered incorrectly by key type after scanning more: expected 'device_eu-central-1_31_zset' to include 'hash'
Raw output
AssertionError: Keys filtered incorrectly by key type after scanning more: expected 'device_eu-central-1_31_zset' to include 'hash'
at Context.<anonymous> (src/tests/browser/filtering.e2e.ts:435:9)
at Generator.next (<anonymous>)
at fulfilled (dist/tests/browser/filtering.e2e.js:5:58)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
Loading