circleci fails on some PRs seemingly because the jobs are not running in the emscripten-core org

[sbc100]

We use some paid-only resources so when jobs run under individual contributors accounts will fail.

For example: #20417

Here is a sample failure URL: https://app.circleci.com/pipelines/github/ericoporto/emscripten/11/workflows/9db52de3-edd6-4d07-95a2-3df36ef3b6c7/jobs/100

"Resource class docker for xlarge is not available for your project, or is not a valid resource class. This message will often appear if the pricing plan for this project does not support docker use."

I can't see any difference between the PRs where things work as expected and the PRs where it fails. Perhaps its a bug in circleCI or perhaps its certain contributors who have certain types of personal circleci accounts?

[sbc100]

Once we collect a few more data points I we report this up to circleci and see if they know what is going on

[imiskolee]

@sbc100 maybe related I also setup a free cricleci for my forked repo.

[RReverser]

I can't see any difference between the PRs where things work as expected and the PRs where it fails. Perhaps its a bug in circleCI or perhaps its certain contributors who have certain types of personal circleci accounts?

As a data point, I ran into this last week when I tried to set up Emscripten's fork in my personal CircleCI too. Then CircleCI decided to use my account for all builds, even for PRs against Emscripten main repo itself.

After I deleted project from my personal CircleCI and restarted build, it chose emscripten org correctly again.