Skip to content

Commit 41b353d

Browse files
tony-gojuanarbol
authored andcommitted
doc: add trace_gc to diagnostic tooling support document
PR-URL: #42346 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]>
1 parent a113d43 commit 41b353d

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

doc/contributing/diagnostic-tooling-support-tiers.md

+3-2
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ The Node.js project has assessed the tools and the APIs which support those
99
tools. Each of the tools and APIs has been put into one of
1010
the following tiers.
1111

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

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

0 commit comments

Comments
 (0)