Skip to content

test: split up test-async-context-frame into individual tests

Rodrigo Muino Tomonari requested to merge github/fork/jasnell/test-async-context-frame-split into main

Using the test runner on these appears to be flaky on windows. This is an experiment to see if splitting these up shows the same flakiness in order to help determine if the issue is with the async-content-frame implementation or the test runner itself.

This PR is opened for testing purposes. It may or may not land. I'm opening it so that I can test the flakiness of these changes in CI.

I do not expect this PR to land as is, and there are several steps to this test meant to use a process of elimination to identify the specifc issue at play. There are three distinct components here that need to be evaluated:

  1. Use of experimental-async-context-frame
  2. Spawning multiple python test runner instances in parallel
  3. Use of node:test to structure the test

Each of these individually or in combination could be leading to the access violation on windows and I've been unable to reproduce the problem locally, so this experiment will work through each using stress tests on the CI

Refs: https://github.com/nodejs/node/issues/54808

Merge request reports