You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, at allure-report we have timeline view with all the used threads and timings. and this timeline uses workerIndex to determine which thread was used.
I found that workerIndex is not always consistent during tests. It can be reproduced when we have a lot of tests of when we repeat each multiple times.
So is it bug that workers have index more than total amount of workers??
reproduction
❯ npm run test -- --repeat-each 5
> pw-primer@1.0.0 test> playwright test --repeat-each 5
Total workers: 2
tesworker index: 0; testName: should allow me to mark all items as completed
tesworker index: 1; testName: should allow me to clear the complete state of all items
tesworker index: 1; testName: should allow me to add todo items
tesworker index: 0; testName: complete all checkbox should update state when items are completed / cleared
tesworker index: 1; testName: should clear text input field when an item is added
tesworker index: 0; testName: should append new items to the bottom of the list
tesworker index: 2; testName: should allow me to mark all items as completed
tesworker index: 3; testName: should allow me to clear the complete state of all items
tesworker index: 2; testName: complete all checkbox should update state when items are completed / cleared
tesworker index: 3; testName: should allow me to add todo items
tesworker index: 2; testName: should clear text input field when an item is added
tesworker index: 3; testName: should append new items to the bottom of the list
tesworker index: 4; testName: should allow me to mark all items as completed
tesworker index: 5; testName: should allow me to clear the complete state of all items
tesworker index: 4; testName: complete all checkbox should update state when items are completed / cleared
The text was updated successfully, but these errors were encountered:
Worker index used for a test is not guaranteed to be the same across test runs, it depends on multiple factors. See this page, worker index will increase when a new worker process is used (e.g. after previous test failures). There is also parallelIndex which may be a better fit for your use. Note that worker index assignment is an implementation detail and it may change in the future depending on the algorithm we use for parallelizing the tests.
Hello, at allure-report we have timeline view with all the used threads and timings. and this timeline uses workerIndex to determine which thread was used.
I found that workerIndex is not always consistent during tests. It can be reproduced when we have a lot of tests of when we repeat each multiple times.
So is it bug that workers have index more than total amount of workers??
reproduction
The text was updated successfully, but these errors were encountered: