Skip to content

fix: Avoid failiure report on successful retry in worker#2141

Merged
DavertMik merged 1 commit into
codeceptjs:masterfrom
KMKoushik:koushik-worker-fix
Jan 18, 2020
Merged

fix: Avoid failiure report on successful retry in worker#2141
DavertMik merged 1 commit into
codeceptjs:masterfrom
KMKoushik:koushik-worker-fix

Conversation

@KMKoushik
Copy link
Copy Markdown
Collaborator

Motivation/Description of the PR

Tests are not reported as passed if the test is passed in a retry while using run-workers.

While appending test status, passing of already failed test is not accounted for. So adding a map with test.id and appending status accordingly fixes the issue.

Type of change

  • Breaking changes
  • New functionality
  • Bug fix
  • Documentation changes/updates
  • Hot fix
  • Markdown files fix - not related to source code

Checklist:

  • Tests have been added
  • Documentation has been added (Run npm run docs)
  • Lint checking (Run npm run lint)
  • Local tests are passed (Run npm test)

@DavertMik
Copy link
Copy Markdown
Contributor

Codacy Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- test/data/sandbox/workers/retry_test.workers.js  1
         

See the complete overview on Codacy

@KMKoushik KMKoushik mentioned this pull request Jan 16, 2020
10 tasks
@KMKoushik KMKoushik requested a review from Vorobeyko January 17, 2020 07:33
Comment thread lib/command/run-workers.js
@DavertMik
Copy link
Copy Markdown
Contributor

@koushikmohan1996 is that compatible with your PR with the refactoring of workers?

@DavertMik
Copy link
Copy Markdown
Contributor

Thank you!

@DavertMik DavertMik merged commit 0a83c2a into codeceptjs:master Jan 18, 2020
@KMKoushik KMKoushik deleted the koushik-worker-fix branch January 26, 2020 11:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Feature Level Retires not being correctly reported with run-workers

4 participants