Microsoft has now doubled our CI capacity (to 20 concurrent VMs for
executing e2e tests).
If the e2e test execution is normalized tomorrow, I will revert the hotfix,
enabling e2e tests on PRs again.
Sorry for the back and forth.
On Tue, May 19, 2020 at 3:11 PM Robert Metzger wrote:
> Microsoft
Microsoft has not increased our capacity yet (even though it was promised
to me yesterday again).
I have now merged a hotfix disabling the e2e test execution on pull
requests to have enough capacity on master.
Please run e2e tests using your private Azure accounts. Thanks for your
understanding!
Roughly speaking, I see the following problematic areas (I have initially
tried running the E2E tests on those machines):
a) e2e tests starting Docker images (including Kubernetes). Since the tests
on the Ali infra are running in docker themselves, we need to adjust the
test scripts (which is not
Thanks for the update Robert.
One idea to make the e2e also run on the Alibaba infrastructure would be to
ensure that e2e tests clean up after they have run. Do we know which e2e
tests don't do this properly?
Cheers,
Till
On Thu, May 14, 2020 at 8:38 AM Robert Metzger wrote:
> Hi all,
>
> tl;d
Hi all,
tl;dr: I will have to cancel some E2E test executions of pull requests
because we have reached the capacity limit of Flink's Azure Pipelines
account.
Long version: We have two types of agent pools in Azure Pipelines:
Microsoft-hosted VMs and Alibaba-hosted Docker environment.
In the Micro
