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

[DRAFT] test_runner: no skip diagnose on warning message #46027

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

MrJithil
Copy link
Contributor

@MrJithil MrJithil commented Dec 31, 2022

test_runner: no skip diagnose on warning message

#45910

@nodejs-github-bot
Copy link
Contributor

nodejs-github-bot commented Dec 31, 2022

Review requested:

@nodejs-github-bot nodejs-github-bot added dont-land-on-v14.x PRs that should not land on the v14.x-staging branch and should not be released in v14.x. needs-ci PRs that need a full CI run. test_runner labels Dec 31, 2022
@MrJithil MrJithil changed the title test_runner: no skip diagnose on warning message [DRAFT] test_runner: no skip diagnose on warning message Dec 31, 2022
@MrJithil MrJithil force-pushed the avoidSkipDiagnoWarns branch 2 times, most recently from 8abd54e to 947cee5 Compare Dec 31, 2022
test_runner: no skip diagnose on warning message
@MoLow
Copy link
Member

MoLow commented Dec 31, 2022

I am not sure regarding this solution and weather it is robust enough

@MoLow
Copy link
Member

MoLow commented Dec 31, 2022

I would prefer a solution that knows what diagnostic messages to ignore, rather than what shouln't

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dont-land-on-v14.x PRs that should not land on the v14.x-staging branch and should not be released in v14.x. needs-ci PRs that need a full CI run. test_runner
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants