e2e:docker tests don't pass locally on master

[fazouane-marouane]

Describe the bug

Running e2e:docker tests fails on master when I clone the repo on my machine

Did you try recovering your dependencies?

No need to recover dependencies

git clone https://github.com/facebook/create-react-app.git
cd create-react-app/
yarn e2e:docker --interactive

Which terms did you search for in User Guide?

e2e, docker

Environment

MacOS 10.14.6
Docker engine 19.03.2
yarn 1.15.2

Steps to reproduce

1. Clone cra locally
2. run e2e tests via docker
3. "e2e-kitchensink.sh" tests fail

Expected behavior

Tests seem to pass for some PRs and on master since a few days ago. I wonder why I cannot run those tests locally or if it's a "known" issue and if there's some workaround that I can use.
Thanks!

Actual behavior

Last logs

lerna info auto-confirmed 
lerna info execute Skipping git tag/commit
lerna info execute Skipping git push
lerna info execute Skipping releases
lerna info publish Publishing packages to npm...
lerna notice Skipping all user and access validation due to third-party registry
lerna notice Make sure you're authenticated properly ¯\_(ツ)_/¯
lerna http fetch PUT 409 http://localhost:4873/babel-plugin-named-asset-import 146ms
lerna http fetch PUT 409 http://localhost:4873/babel-preset-react-app 55ms
lerna http fetch GET 200 http://localhost:4873/babel-plugin-named-asset-import?write=true 77ms
lerna ERR! EPUBLISHCONFLICT Cannot publish babel-plugin-named-asset-import@undefined over existing version.
++ set +x
e2e-kitchensink.sh: ERROR! An error was encountered executing line 84.
Cleaning up.

[stale]

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.

[fazouane-marouane]

This is still a problem and it’s blocking me from contributing to this repo 😕 so I’m not closing this issue without a tip or workaround

[iansu]

There are two options:

1. Fix the tests so they run locally
2. Make a PR and it will run the tests on our CI

The docker tests being broken is a known issue. We would love to fix it but only have so much time.

[fazouane-marouane]

Thanks for the response! I thought that I was doing something wrong on my end. Originally, I have PR #6599 where CI always failed on it but couldn't reproduce it locally. Now I know why. I'll see if I can fix anything related to this.