Chris Selzo

based on the code here, it seems like we could probs either use it, or write something that runs on pws that would do this for us? https://github.com/evertonfraga/probot-auto-assigner

Is this something we're still interested in doing? It seems liable to break a lot of things with no clear benefit (other than brevity).

We found the changes in runc that lead to this behavioral change: https://github.com/opencontainers/runc/commit/a6f4081766a0f405bb9b5e798a4930c1f434c6b1 and https://github.com/opencontainers/runc/commit/7396ca90fa47d0458da4188061b24ca1bff465bf Essentially, errors from removing cgroups were being ignored. Now they're taking a "fast fail" approach....

Note that this only appears to be a problem with bosh lites using the `warden` cpi, not the `docker` cpi.

FYI I've opened a PR for bosh-deployment to resolve this issue: https://github.com/cloudfoundry/bosh-deployment/pull/479

No, it does not happen with the cf7 beta, at least version `7.0.0-beta.24+71d763254.2019-08-20`

I don't think it's a bug in the v2 CC API per se - the `q` parameter that the CLI uses to ask for routes with the given host/path/domain (without...

If we are ok with the cost, the simplest thing to do would be to deploy a single windows 2019 worker in the FIWG concourse and move the pipeline over...

Our internal windows workers are configured like ```yaml cpu: 8 ram: 32768 disk: 524288 ``` which is roughly equivalent to `e2-standard-8` I think?

Also something I just realized is that the integration tests rely on a persistent bosh director that we have deployed, so we'd need either one of those in the CFF...