Skip to content

Commit

Permalink
doc: add trace_gc to diagnostic tooling support document
Browse files Browse the repository at this point in the history
PR-URL: #42346
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
  • Loading branch information
tony-go authored and juanarbol committed Apr 6, 2022
1 parent d302d2f commit 48bd9fa
Showing 1 changed file with 3 additions and 2 deletions.
5 changes: 3 additions & 2 deletions doc/contributing/diagnostic-tooling-support-tiers.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ The Node.js project has assessed the tools and the APIs which support those
tools. Each of the tools and APIs has been put into one of
the following tiers.

* Tier 1 - Must always be working(CI tests passing) for all
* Tier 1 - Must always be working (CI tests passing) for all
Current and LTS Node.js releases. A release will not be shipped if the test
suite for the tool/API is not green. To be considered for inclusion
in this tier it must have a good test suite and that test suite and a job
Expand All @@ -29,7 +29,7 @@ the following tiers.
its dependencies; and
* The tool must be open source.

* Tier 2 - Must be working(CI tests passing) for all
* Tier 2 - Must be working (CI tests passing) for all
LTS releases. An LTS release will not be shipped if the test
suite for the tool/API is not green. To be considered for inclusion
in this tier it must have a good test suite and that test suite and a job
Expand Down Expand Up @@ -136,6 +136,7 @@ The tools are currently assigned to Tiers as follows:
| Debugger | Chrome Dev tools | ? | No | 3 |
| Debugger | Chakracore - time-travel | No | Data source only | too early |
| Tracing | trace\_events (API) | No | Yes | 1 |
| Tracing | trace\_gc | No | Yes | 1 |
| Tracing | DTrace | No | Partial | 3 |
| Tracing | LTTng | No | Removed? | N/A |
| Tracing | ETW | No | Partial | 3 |
Expand Down

0 comments on commit 48bd9fa

Please sign in to comment.