-
-
Notifications
You must be signed in to change notification settings - Fork 4.9k
fix: unify timing report for concurrent linting #20188
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
Conversation
✅ Deploy Preview for docs-eslint canceled.
|
|
When I test this locally, with this project, it prints 3 extra headers for the table: Not sure why and how this happens. |
|
@mdjermanovic I tested this multiple times locally, but I’m not getting the extra headers |
|
I'm still getting extra headers, but it's interesting that I'm also getting one extra header on the Anyone else getting the same? It could be that some of the eslint plugins we're using is doing something unusual, like importing Linter. |
I'm not getting multiple headers with |
|
Okay, I got it. |
fasttime
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks! Leaving open for @mdjermanovic to review.
mdjermanovic
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
Prerequisites checklist
What is the purpose of this pull request? (put an "X" next to an item)
[ ] Documentation update
[x] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofix to a rule
[ ] Add a CLI option
[ ] Add something to the core
[ ] Other, please explain:
What changes did you make? (Give an overview)
When running ESLint with
--concurrency, multiple timing reports were generated — one per worker thread — resulting in fragmented timing data.This change ensures that timing information is collected and merged into a single unified report, matching the behavior seen when linting without concurrency.
getData()to expose per-rule timing totals from each worker.mergeData()to aggregate worker timings in the main thread.Fixes #20063
Is there anything you'd like reviewers to focus on?