{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":40613511,"defaultBranch":"master","name":"node","ownerLogin":"cjihrig","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2015-08-12T17:07:21.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/2512748?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1726410112.0","currentOid":""},"activityList":{"items":[{"before":"808d7adf769444ada49b2425b804e296c291f870","after":"81e000d470d2d4a2ff78e7ebbde2d7492e9b631a","ref":"refs/heads/summary","pushedAt":"2024-09-20T14:21:20.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"cjihrig","name":"Colin Ihrig","path":"/cjihrig","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2512748?s=80&v=4"},"commit":{"message":"squash: rename 'all' to 'tests'","shortMessageHtmlLink":"squash: rename 'all' to 'tests'"}},{"before":"f5d9d926ebf2491a7f6c430aff72efcf3010b5c0","after":null,"ref":"refs/heads/no-only","pushedAt":"2024-09-15T14:21:52.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"cjihrig","name":"Colin Ihrig","path":"/cjihrig","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2512748?s=80&v=4"}},{"before":"dfcbb8606469fe0099695e6b358314fcfde11a72","after":"808d7adf769444ada49b2425b804e296c291f870","ref":"refs/heads/summary","pushedAt":"2024-09-14T19:22:38.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"cjihrig","name":"Colin Ihrig","path":"/cjihrig","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2512748?s=80&v=4"},"commit":{"message":"test_runner: add 'test:summary' event\n\nThis commit adds a new 'test:summary' event to the test runner's\nreporting interface. This new event serves two purposes:\n\n- In the future, the test runner internals will no longer need to\n  change the process exit code. This may be important to run()\n  users. Unfortunately, this is a breaking change, so it needs to\n  be changed in a major version.\n- The reporting interface now has a single event that can identify\n  passing or failing test runs.\n\nRefs: https://github.com/nodejs/node/issues/53867\nRefs: https://github.com/nodejs/node/issues/54812","shortMessageHtmlLink":"test_runner: add 'test:summary' event"}},{"before":"b5254f966fd276463bba4a7dbd97e4253feec9c8","after":"dfcbb8606469fe0099695e6b358314fcfde11a72","ref":"refs/heads/summary","pushedAt":"2024-09-14T19:17:49.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"cjihrig","name":"Colin Ihrig","path":"/cjihrig","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2512748?s=80&v=4"},"commit":{"message":"test_runner: add 'test:summary' event\n\nThis commit adds a new 'test:summary' event to the test runner's\nreporting interface. This new event serves two purposes:\n\n- In the future, the test runner internals will no longer need to\n  change the process exit code. This may be important to run()\n  users. Unfortunately, this is a breaking change, so it needs to\n  be changed in a major version.\n- The reporting interface now has a single event that can identify\n  passing or failing test runs.\n\nRefs: https://github.com/nodejs/node/issues/53867\nRefs: https://github.com/nodejs/node/issues/54812","shortMessageHtmlLink":"test_runner: add 'test:summary' event"}},{"before":"905432ef0d73948523226547e16ebed2afdfbb2a","after":"f5d9d926ebf2491a7f6c430aff72efcf3010b5c0","ref":"refs/heads/no-only","pushedAt":"2024-09-12T17:19:17.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"cjihrig","name":"Colin Ihrig","path":"/cjihrig","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2512748?s=80&v=4"},"commit":{"message":"squash: add a test","shortMessageHtmlLink":"squash: add a test"}},{"before":"d411031b1a3b0b22362a489e2c887fd55f7f160c","after":"905432ef0d73948523226547e16ebed2afdfbb2a","ref":"refs/heads/no-only","pushedAt":"2024-09-12T17:15:47.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"cjihrig","name":"Colin Ihrig","path":"/cjihrig","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2512748?s=80&v=4"},"commit":{"message":"test_runner: detect only tests when --test is not used\n\nThis commit updates the way the test runner processes 'only'\ntests when node:test files are run without the --test CLI.\nThis is a breaking change.","shortMessageHtmlLink":"test_runner: detect only tests when --test is not used"}},{"before":"f5f67ae4a76f15df47fdf3f1253aba695c3d0ab9","after":null,"ref":"refs/heads/isolation-only","pushedAt":"2024-09-12T16:57:50.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"cjihrig","name":"Colin Ihrig","path":"/cjihrig","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2512748?s=80&v=4"}},{"before":"03fb9e8a98dc0a496249a964ed1cb8a246a84822","after":"f5f67ae4a76f15df47fdf3f1253aba695c3d0ab9","ref":"refs/heads/isolation-only","pushedAt":"2024-09-12T16:57:30.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"cjihrig","name":"Colin Ihrig","path":"/cjihrig","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2512748?s=80&v=4"},"commit":{"message":"test_runner: detect only tests when isolation is off\n\nThis commit updates the way the test runner processes 'only'\ntests when process-based test isolation is disabled. The\n--test-only flag is no longer necessary in this scenario. The\ntest runner will automatically detect 'only' tests and apply the\nappropriate filtering.\n\nPR-URL: https://github.com/nodejs/node/pull/54832\nReviewed-By: Chemi Atlow <chemi@atlow.co.il>\nReviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>\nReviewed-By: James M Snell <jasnell@gmail.com>\nReviewed-By: Moshe Atlow <moshe@atlow.co.il>","shortMessageHtmlLink":"test_runner: detect only tests when isolation is off"}},{"before":"4b39649fd6fb546e753ba0c76454c87ef2c42c08","after":null,"ref":"refs/heads/coverage-cleanup","pushedAt":"2024-09-11T13:53:35.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"cjihrig","name":"Colin Ihrig","path":"/cjihrig","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2512748?s=80&v=4"}},{"before":null,"after":"d411031b1a3b0b22362a489e2c887fd55f7f160c","ref":"refs/heads/no-only","pushedAt":"2024-09-10T21:01:36.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"cjihrig","name":"Colin Ihrig","path":"/cjihrig","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2512748?s=80&v=4"},"commit":{"message":"test_runner: detect only tests when --test is not used\n\nThis commit updates the way the test runner processes 'only'\ntests when node:test files are run without the --test CLI.\nThis is a breaking change.","shortMessageHtmlLink":"test_runner: detect only tests when --test is not used"}},{"before":"1c54d7f34411c05f3a6f4c7d63792c30fca7076f","after":"03fb9e8a98dc0a496249a964ed1cb8a246a84822","ref":"refs/heads/isolation-only","pushedAt":"2024-09-10T12:47:36.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"cjihrig","name":"Colin Ihrig","path":"/cjihrig","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2512748?s=80&v=4"},"commit":{"message":"test_runner: detect only tests when isolation is off\n\nThis commit updates the way the test runner processes 'only'\ntests when process-based test isolation is disabled. The\n--test-only flag is no longer necessary in this scenario. The\ntest runner will automatically detect 'only' tests and apply the\nappropriate filtering.","shortMessageHtmlLink":"test_runner: detect only tests when isolation is off"}},{"before":"99a3b187fec0520f5385f48cdc071e5fc64fab1e","after":"4b39649fd6fb546e753ba0c76454c87ef2c42c08","ref":"refs/heads/coverage-cleanup","pushedAt":"2024-09-09T02:44:26.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"cjihrig","name":"Colin Ihrig","path":"/cjihrig","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2512748?s=80&v=4"},"commit":{"message":"test_runner: improve code coverage cleanup\n\nThe test runner's code coverage leaves old coverage data in the\ntemp directory. This commit updates the cleanup logic to:\n\n- Stop code collection. Otherwise V8 would write collection data\n  again when the process exits.\n- Remove the temp directory containing the coverage data.\n- Attempt to clean up the coverage data even if parsing the\n  data resulted in an error.\n\nWith this change, I no longer see any coverage data left behind\nin the system temp directory.\n\nRefs: https://github.com/nodejs/build/issues/3864\nRefs: https://github.com/nodejs/build/issues/3887","shortMessageHtmlLink":"test_runner: improve code coverage cleanup"}},{"before":null,"after":"99a3b187fec0520f5385f48cdc071e5fc64fab1e","ref":"refs/heads/coverage-cleanup","pushedAt":"2024-09-09T02:36:57.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"cjihrig","name":"Colin Ihrig","path":"/cjihrig","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2512748?s=80&v=4"},"commit":{"message":"test_runner: improve code coverage cleanup\n\nThe test runner's code coverage leaves old coverage data in the\ntemp directory. This commit updates the cleanup logic to:\n\n- Stop code collection. Otherwise V8 would write collection data\n  again when the process exits.\n- Remove the temp directory containing the coverage data.\n- Attempt to clean up the coverage data even if parsing the\n  data resulted in an error.\n\nWith this change, I no longer see any coverage data left behind\nin the system temp directory.\n\nRefs: https://github.com/nodejs/build/issues/3864\nRefs: https://github.com/nodejs/build/issues/3887","shortMessageHtmlLink":"test_runner: improve code coverage cleanup"}},{"before":null,"after":"b5254f966fd276463bba4a7dbd97e4253feec9c8","ref":"refs/heads/summary","pushedAt":"2024-09-08T20:25:47.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"cjihrig","name":"Colin Ihrig","path":"/cjihrig","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2512748?s=80&v=4"},"commit":{"message":"test_runner: add 'test:summary' event\n\nThis commit adds a new 'test:summary' event to the test runner's\nreporting interface. This new event serves two purposes:\n\n- The test runner internals no longer change the process exit\n  code. This may be important to run() users.\n- The reporting interface now has a single event that can identify\n  passing or failing test runs.\n\nRefs: https://github.com/nodejs/node/issues/53867\nRefs: https://github.com/nodejs/node/issues/54812","shortMessageHtmlLink":"test_runner: add 'test:summary' event"}},{"before":null,"after":"1c54d7f34411c05f3a6f4c7d63792c30fca7076f","ref":"refs/heads/isolation-only","pushedAt":"2024-09-07T15:19:21.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"cjihrig","name":"Colin Ihrig","path":"/cjihrig","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2512748?s=80&v=4"},"commit":{"message":"test_runner: detect only tests when isolation is off\n\nThis commit updates the way the test runner processes 'only'\ntests when process-based test isolation is disabled. The\n--test-only flag is no longer necessary in this scenario. The\ntest runner will automatically detect 'only' tests and apply the\nappropriate filtering.","shortMessageHtmlLink":"test_runner: detect only tests when isolation is off"}},{"before":"dfdbbe4835f1f383576a7b5cfeeb55e100456ef4","after":null,"ref":"refs/heads/default-reporter","pushedAt":"2024-08-27T15:24:45.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"cjihrig","name":"Colin Ihrig","path":"/cjihrig","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2512748?s=80&v=4"}},{"before":"031aba50e21dd77ea859f386f8c3b66ed8e7eedd","after":"dfdbbe4835f1f383576a7b5cfeeb55e100456ef4","ref":"refs/heads/default-reporter","pushedAt":"2024-08-27T01:23:29.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"cjihrig","name":"Colin Ihrig","path":"/cjihrig","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2512748?s=80&v=4"},"commit":{"message":"test_runner: always make spec the default reporter\n\nThis is a breaking change. Prior to this commit, the test_runner\ndefaulted to the spec reporter if using a TTY, and the TAP\nreporter otherwise. This commit makes spec the default reporter\nunconditionally. TAP output is still available via the\n--test-reporter=tap CLI flag.\n\nFixes: https://github.com/nodejs/node/issues/54540","shortMessageHtmlLink":"test_runner: always make spec the default reporter"}},{"before":"d14e5ca0a603f7ac3972007500f169e7b2be7de8","after":null,"ref":"refs/heads/reporter-tests","pushedAt":"2024-08-27T01:18:20.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"cjihrig","name":"Colin Ihrig","path":"/cjihrig","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2512748?s=80&v=4"}},{"before":"9b3fab5f2628d07c33b517a6dcf4c6e7a993657a","after":"d14e5ca0a603f7ac3972007500f169e7b2be7de8","ref":"refs/heads/reporter-tests","pushedAt":"2024-08-26T15:37:52.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"cjihrig","name":"Colin Ihrig","path":"/cjihrig","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2512748?s=80&v=4"},"commit":{"message":"this is why we don't touch unrelated things","shortMessageHtmlLink":"this is why we don't touch unrelated things"}},{"before":"c6c92c222c7ad21b0608d8a26f38a41ed2b55a32","after":"9b3fab5f2628d07c33b517a6dcf4c6e7a993657a","ref":"refs/heads/reporter-tests","pushedAt":"2024-08-26T13:25:56.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"cjihrig","name":"Colin Ihrig","path":"/cjihrig","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2512748?s=80&v=4"},"commit":{"message":"test: refactor test_runner tests to change default reporter\n\nThis commit updates the test runner tests in order to switch the\ndefault reporter from tap to spec. This commit can be backported,\nwhile changing the default reporter cannot.\n\nRefs: https://github.com/nodejs/node/issues/54540","shortMessageHtmlLink":"test: refactor test_runner tests to change default reporter"}},{"before":"1fc1ba810747dd25a1c47ea545bb02579eb8fc50","after":null,"ref":"refs/heads/tap-fix","pushedAt":"2024-08-26T13:20:42.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"cjihrig","name":"Colin Ihrig","path":"/cjihrig","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2512748?s=80&v=4"}},{"before":"efd61763a16f23b6efaa96292f4064b88dfcce7b","after":"c6c92c222c7ad21b0608d8a26f38a41ed2b55a32","ref":"refs/heads/reporter-tests","pushedAt":"2024-08-25T14:12:22.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"cjihrig","name":"Colin Ihrig","path":"/cjihrig","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2512748?s=80&v=4"},"commit":{"message":"test: refactor test_runner tests to change default reporter\n\nThis commit updates the test runner tests in order to switch the\ndefault reporter from tap to spec. This commit can be backported,\nwhile changing the default reporter cannot.\n\nRefs: https://github.com/nodejs/node/issues/54540","shortMessageHtmlLink":"test: refactor test_runner tests to change default reporter"}},{"before":null,"after":"031aba50e21dd77ea859f386f8c3b66ed8e7eedd","ref":"refs/heads/default-reporter","pushedAt":"2024-08-24T23:25:18.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"cjihrig","name":"Colin Ihrig","path":"/cjihrig","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2512748?s=80&v=4"},"commit":{"message":"test_runner: always make spec the default reporter\n\nThis is a breaking change. Prior to this commit, the test_runner\ndefaulted to the spec reporter if using a TTY, and the TAP\nreporter otherwise. This commit makes spec the default reporter\nunconditionally. TAP output is still available via the\n--test-reporter=tap CLI flag.\n\nFixes: https://github.com/nodejs/node/issues/54540","shortMessageHtmlLink":"test_runner: always make spec the default reporter"}},{"before":null,"after":"efd61763a16f23b6efaa96292f4064b88dfcce7b","ref":"refs/heads/reporter-tests","pushedAt":"2024-08-24T23:24:42.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"cjihrig","name":"Colin Ihrig","path":"/cjihrig","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2512748?s=80&v=4"},"commit":{"message":"test: refactor test_runner tests to change default reporter\n\nThis commit updates the test runner tests in order to switch the\ndefault reporter from tap to spec. This commit can be backported,\nwhile changing the default reporter cannot.\n\nRefs: https://github.com/nodejs/node/issues/54540","shortMessageHtmlLink":"test: refactor test_runner tests to change default reporter"}},{"before":"d7b5a2055c5530cf4e9579294353704ebdd9232a","after":"1fc1ba810747dd25a1c47ea545bb02579eb8fc50","ref":"refs/heads/tap-fix","pushedAt":"2024-08-24T14:41:37.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"cjihrig","name":"Colin Ihrig","path":"/cjihrig","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2512748?s=80&v=4"},"commit":{"message":"test: force spec reporter in test-runner-watch-mode.mjs\n\nIn the CI this test generates TAP output that can confuse the\nPython test runner. Avoid the problem by not outputting TAP at\nfrom the spawned child process.\n\nFixes: https://github.com/nodejs/node/issues/54535","shortMessageHtmlLink":"test: force spec reporter in test-runner-watch-mode.mjs"}},{"before":"6dbe95ca25441b582697e1b46f3d9e5b7c4ea564","after":"d7b5a2055c5530cf4e9579294353704ebdd9232a","ref":"refs/heads/tap-fix","pushedAt":"2024-08-24T12:47:40.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"cjihrig","name":"Colin Ihrig","path":"/cjihrig","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2512748?s=80&v=4"},"commit":{"message":"remove tap from child process too","shortMessageHtmlLink":"remove tap from child process too"}},{"before":null,"after":"6dbe95ca25441b582697e1b46f3d9e5b7c4ea564","ref":"refs/heads/tap-fix","pushedAt":"2024-08-24T12:36:44.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"cjihrig","name":"Colin Ihrig","path":"/cjihrig","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2512748?s=80&v=4"},"commit":{"message":"test: force spec reporter in test-runner-watch-mode.mjs\n\nIn the CI this test generates TAP output that can confuse the\nPython test runner. Avoid the problem by not outputting TAP at\nall.\n\nFixes: https://github.com/nodejs/node/issues/54535","shortMessageHtmlLink":"test: force spec reporter in test-runner-watch-mode.mjs"}},{"before":"c96455c2888395c92e4ad0598e8f68e3851019d4","after":null,"ref":"refs/heads/isolation","pushedAt":"2024-08-21T13:39:52.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"cjihrig","name":"Colin Ihrig","path":"/cjihrig","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2512748?s=80&v=4"}},{"before":"3b05904408c6eb0b908ecc8ee7a9988c20bd4929","after":null,"ref":"refs/heads/coverage-bug","pushedAt":"2024-08-21T02:40:27.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"cjihrig","name":"Colin Ihrig","path":"/cjihrig","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2512748?s=80&v=4"}},{"before":"ef6b5d99e6d260e1487cc3436af9ab7a8fc1f1ea","after":"c96455c2888395c92e4ad0598e8f68e3851019d4","ref":"refs/heads/isolation","pushedAt":"2024-08-20T23:31:44.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"cjihrig","name":"Colin Ihrig","path":"/cjihrig","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2512748?s=80&v=4"},"commit":{"message":"test_runner: support running tests in process\n\nThis commit introduces a new --experimental-test-isolation flag\nthat, when set to 'none', causes the test runner to execute all\ntests in the same process. By default, this is the main test\nrunner process, but if watch mode is enabled, it spawns a separate\nprocess that runs all of the tests.\n\nThe default value of the new flag is 'process', which uses the\nexisting behavior of running each test file in its own child\nprocess.\n\nIt is worth noting that when the isolation mode is 'none', globals\nand all other top level logic (such as top level before() and after()\nhooks) is shared among all files.\n\nCo-authored-by: Moshe Atlow <moshe@atlow.co.il>","shortMessageHtmlLink":"test_runner: support running tests in process"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEvAz5wgA","startCursor":null,"endCursor":null}},"title":"Activity · cjihrig/node"}