Skip to content

test: reduce iteration count in test-child-process-stdout-flush-exit #58273

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

Merged
merged 1 commit into from
May 13, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion test/parallel/test-child-process-stdout-flush-exit.js
Original file line number Diff line number Diff line change
Expand Up @@ -25,9 +25,14 @@ const assert = require('assert');

// If child process output to console and exit
// The console.log statements here are part of the test.
// Note: This test verifies specific behavior that is *not* guaranteed
// by Node.js's API contract. See https://nodejs.org/api/process.html#processexitcode.
// We are still generally interested in knowing when this test breaks,
// since applications may rely on the implicit behavior of stdout having
// a buffer size up to which they can write data synchronously.
if (process.argv[2] === 'child') {
console.log('hello');
for (let i = 0; i < 200; i++) {
for (let i = 0; i < 100; i++) {
console.log('filler');
}
console.log('goodbye');
Expand Down
Loading