-
Notifications
You must be signed in to change notification settings - Fork 150
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
lib: drop skipped modules #1036
Conversation
This module isn't being tested in our CITGM for one of the following reasons: * "skip" is true - meaning we're skipping it into CITGM run * ">= EOL version" - meaning this module is being skipped in all active release lines
This module isn't being tested in our CITGM for one of the following reasons: * "skip" is true - meaning we're skipping it into CITGM run * ">= EOL version" - meaning this module is being skipped in all active release lines
This module isn't being tested in our CITGM for one of the following reasons: * "skip" is true - meaning we're skipping it into CITGM run * ">= EOL version" - meaning this module is being skipped in all active release lines
This module isn't being tested in our CITGM for one of the following reasons: * "skip" is true - meaning we're skipping it into CITGM run * ">= EOL version" - meaning this module is being skipped in all active release lines
This module isn't being tested in our CITGM for one of the following reasons: * "skip" is true - meaning we're skipping it into CITGM run * ">= EOL version" - meaning this module is being skipped in all active release lines
This module isn't being tested in our CITGM for one of the following reasons: * "skip" is true - meaning we're skipping it into CITGM run * ">= EOL version" - meaning this module is being skipped in all active release lines
This module isn't being tested in our CITGM for one of the following reasons: * "skip" is true - meaning we're skipping it into CITGM run * ">= EOL version" - meaning this module is being skipped in all active release lines
This module isn't being tested in our CITGM for one of the following reasons: * "skip" is true - meaning we're skipping it into CITGM run * ">= EOL version" - meaning this module is being skipped in all active release lines
This module isn't being tested in our CITGM for one of the following reasons: * "skip" is true - meaning we're skipping it into CITGM run * ">= EOL version" - meaning this module is being skipped in all active release lines
This module isn't being tested in our CITGM for one of the following reasons: * "skip" is true - meaning we're skipping it into CITGM run * ">= EOL version" - meaning this module is being skipped in all active release lines
This module isn't being tested in our CITGM for one of the following reasons: * "skip" is true - meaning we're skipping it into CITGM run * ">= EOL version" - meaning this module is being skipped in all active release lines
This module isn't being tested in our CITGM for one of the following reasons: * "skip" is true - meaning we're skipping it into CITGM run * ">= EOL version" - meaning this module is being skipped in all active release lines
This module isn't being tested in our CITGM for one of the following reasons: * "skip" is true - meaning we're skipping it into CITGM run * ">= EOL version" - meaning this module is being skipped in all active release lines
This module isn't being tested in our CITGM for one of the following reasons: * "skip" is true - meaning we're skipping it into CITGM run * ">= EOL version" - meaning this module is being skipped in all active release lines
This module isn't being tested in our CITGM for one of the following reasons: * "skip" is true - meaning we're skipping it into CITGM run * ">= EOL version" - meaning this module is being skipped in all active release lines
This module isn't being tested in our CITGM for one of the following reasons: * "skip" is true - meaning we're skipping it into CITGM run * ">= EOL version" - meaning this module is being skipped in all active release lines
This module isn't being tested in our CITGM for one of the following reasons: * "skip" is true - meaning we're skipping it into CITGM run * ">= EOL version" - meaning this module is being skipped in all active release lines
This module isn't being tested in our CITGM for one of the following reasons: * "skip" is true - meaning we're skipping it into CITGM run * ">= EOL version" - meaning this module is being skipped in all active release lines
This module isn't being tested in our CITGM for one of the following reasons: * "skip" is true - meaning we're skipping it into CITGM run * ">= EOL version" - meaning this module is being skipped in all active release lines
This module isn't being tested in our CITGM for one of the following reasons: * "skip" is true - meaning we're skipping it into CITGM run * ">= EOL version" - meaning this module is being skipped in all active release lines
This module isn't being tested in our CITGM for one of the following reasons: * "skip" is true - meaning we're skipping it into CITGM run * ">= EOL version" - meaning this module is being skipped in all active release lines
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1036 +/- ##
==========================================
+ Coverage 95.23% 96.33% +1.10%
==========================================
Files 28 28
Lines 2181 2181
==========================================
+ Hits 2077 2101 +24
+ Misses 104 80 -24 ☔ View full report in Codecov by Sentry. |
Now I'm pinging module authors to inform them that the modules are being removed from If you believe your module isn't flaky anymore and should be included in the CITGM for all active release lines, please open a PR I'll be happy to review/approve it. @devinivy @DavidTPate @AdriVanHoudt Again, no action other than removing the modules should be made in this PR. I'm planning to merge it tomorrow. |
Following up on the recent bankruptcy of the CITGM, this PR removes all modules that are being skipped by either having a "skip: true" or because we're skipping all active release lines, for instance: ">= 17" or ">= 16". I know that the idea of "skip: true" was temporary, but some modules have been skipped for quite some time.
My suggestion for the modules that still want to be included in the current CITGM is to open a new PR to add it back so we guarantee our CITGM will not be red/failing until issues are fixed - please note a flaky CITGM affects directly the efforts of a release.
Before pinging module authors I'd like to get @nodejs/tsc approval since the list is big and I don't want to cause any more noise in their notification box.