Pietro Marchini
Pietro Marchini
@cjihrig thanks for the support, I'm gonna take a look ASAP!
> It looks like there may be relevant failures in the latest CI run. Hey @cjihrig, yes I've seen, I'm preparing my Windows build!
@cjihrig after some attempts I was able to reproduce the same errors on my Windows 10 machine. I'll take a look ASAP, it's definitely flaky
@cjihrig, I'm still looking into this. I've been able to replicate it 3 times in 12 hours, after thousands of retries
Hey @cjihrig, I have just pushed a debug-only commit, I will revert it later. In my local Windows environment, something very strange is happening: The error, like the one we...
I'll take a look ASAP
Hey @cjihrig, I just took a quick look and the fixtures are not using `only`. Given one.test.js: ```js suite('suite one', function() { record(this.name); test('suite one - test', { only: true...
> > I just took a quick look and the fixtures are not using only. > > I believe it is: > > > test('suite one - test', { only:...
@cjihrig, but still, do you think it makes sense to have two different behaviors based on the isolation? Honestly, I wasn't expecting this. Note: ```sh > ./node --test --experimental-test-isolation=none test/fixtures/test-runner/no-isolation/one.test.js...
> > do you think it makes sense to have two different behaviors based on the isolation? > > For the `only` flag, I do. When running multiple test processes...