Nightwatch artifacts on GitLab not retained

Seems fine to me.

Would love to know why nightwatch is failing so frequently in gitlab this last week.

Should we set DRUPAL_NIGHTWATCH_OUTPUT to ../nightwatch_output instead? Feels a bit wrong writing inside the core directory, which is part of the checkout.

Sure, just wanted to maintain the original setting of DRUPAL_NIGHTWATCH_OUTPUT.

Question about the mkdir/chown lines - not sure these are needed even if it's working without it!

I think we lost babel, along with its caching somewhere around #3278415: Remove usages of the JavaScript ES6 build step, the build step itself, and associated dev dependencies → ?

This seems to be the minimal mkdir-s that would be otherwise created through Drupal and the minimal chown-s to work/prevent warnings.

Well, I stand corrected, all mkdir-s are not needed.

Leaning on this didn't break anything it seems and am seeing artifacts here https://git.drupalcode.org/issue/drupal-3401102/-/jobs/335835/artifacts/...

Also seeing Nightwatch results now at https://git.drupalcode.org/issue/drupal-3401102/-/pipelines/50024/test_r...

Great work!

Committed and pushed 93eb23400e to 11.x and b71596d090 to 10.2.x. Thanks!

I wasn't expecting it to backport cleanly to 10.1.x, but it did, so cherry-picked it there too.

Spokje → closed merge request !5361

Automatically closed - issue fixed for 2 weeks with no activity.