Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: revert do not run parallel mode when you have only one file #146

Conversation

alexander-akait
Copy link
Member

This PR contains a:

  • bugfix
  • new feature
  • code refactor
  • test update
  • typo fix
  • metadata update

Motivation / Use-Case

Revert, this often leads to memory overflow, so it is best to always use an external process

Breaking Changes

No

Additional Info

No

@codecov
Copy link

codecov bot commented Sep 6, 2019

Codecov Report

Merging #146 into master will not change coverage.
The diff coverage is 100%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #146   +/-   ##
=======================================
  Coverage   99.29%   99.29%           
=======================================
  Files           5        5           
  Lines         282      282           
  Branches      111      111           
=======================================
  Hits          280      280           
  Misses          2        2
Impacted Files Coverage Δ
src/index.js 99.35% <100%> (ø) ⬆️
src/TaskRunner.js 100% <100%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 815e533...935519e. Read the comment docs.

@alexander-akait alexander-akait merged commit 6613a97 into master Sep 6, 2019
@alexander-akait alexander-akait deleted the fix-revert-do-not-run-parallel-mode-when-you-have-only-one-file branch September 6, 2019 14:12
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.

None yet

1 participant