Need test runners without bytecode caching

I think there should be a category of bots which check only per commit, more in an advisory than in a mandatory capacity and this should be one of them. I would even argue that the non-mysql bots should be too.

Ideally we would have some static analysis tools which would cover the particular problem mentioned. Does someone know of such a tool?

So I think running every patch would be a complete waste.

Running post-commit would be useful enough.

A bonus might be running the additional environments when a patch reaches RTBC.

Choosing which environments run is a job at the dispatch level.

This issue, however, is about ensuring we have a non-opcode test runner that the dispatch can route tests too. How best do we do this within the test runner?

Options:
- separate test type for non-opcode testing? (yuck)
- disable_opcode flag in the test definition? (Need to explore how best to disable it ... if we have steps, we can build this into the test-runner logic, possibly as a pre-execute command/script)
- other?

php.ini chunks in the job yaml?

Hmmm ... a 'setup: php:' plugin, which takes php.ini chunks as a value, which adds those chunks to the ini file and restarts PHP before executing actual tests would work ... at least an idea worth exploring further.

Moved to DrupalCI Environments.

Postponing on https://www.drupal.org/node/2607876

Im going to go ahead and close this. opcode caching is available in all supported versions of php by default, so I dont think this is a scenario we need to test for.