After #39555 is merged, the "experimental" Jenkins doesn't seem to be running anything different than the regular (Janky) tests, so we're just running the exact same tests twice, on the same architecture and server configuration.
If new experimental features are added, we could enable experimental by default on the main daemon, or for the remaining tests, spin up a new daemon as part of the test.
Tests that require experimental (or use experimental):
| Test(s) |
Notes |
TestExternalGraphDriver |
tests start a new daemon with experimental, so main daemon doesn't have to be experimental |
TestGraphdriverPluginV2 |
tests start a new daemon with experimental, so main daemon doesn't have to be experimental |
TestBuildSquashParent |
tests start a new daemon with experimental, so main daemon doesn't have to be experimental |
TestServicePlugin |
tests start a new daemon with experimental, so main daemon doesn't have to be experimentalexperimental |
TestAuthZ**** |
tests start a new daemon with experimental, so main daemon doesn't have to be experimental |
After #39555 is merged, the "experimental" Jenkins doesn't seem to be running anything different than the regular (Janky) tests, so we're just running the exact same tests twice, on the same architecture and server configuration.
If new experimental features are added, we could enable
experimentalby default on the main daemon, or for the remaining tests, spin up a new daemon as part of the test.Tests that require experimental (or use experimental):
TestExternalGraphDriverTestGraphdriverPluginV2TestBuildSquashParentTestServicePluginTestAuthZ****