-
-
Notifications
You must be signed in to change notification settings - Fork 31.6k
test-ttywrap.writestream.js test always passes #28304
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
That’s because the test isn’t run in that case, I assume; it’s As for the failure, I assume the missing before/after hooks would have been corresponding to the Tbh, I’d just remove the test file. |
I can get behind that: #28316 |
The test is never run in CI and may have never worked. Refs: nodejs#28304 PR-URL: nodejs#28316 Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: James M Snell <jasnell@gmail.com>
Closing as the test was removed in b448db3. |
In
test/async-hooks/test-ttywrap.writestream.js
, there isdelayedOnCloseHandler()
which is supposed to check the async-hooks graph. When I run directly with thenode
executable, the test fails. When run withtools/test.py
, though, the test passes. On my computer, at least, I can change the contents ofdelayedOnCloseHandler()
to anything. It can just be athrow
statement. The test will fail as expected when run directly withnode
but will pass when run withtools/test.py
.First, can someone else confirm this so that we can label this with
confirmed-bug
(or find that they don't experience this behavior in which case I can look more closely at exactly what I'm doing wrong).Second, does anyone know why this would be the case?
@nodejs/testing @nodejs/async_hooks
The text was updated successfully, but these errors were encountered: