mirror of
https://github.com/featurebasedb/featurebase.git
synced 2026-09-15 16:51:03 +00:00
ebd0fa85fa
mark IDK tests and batch tests as "nonblocking" so we don't wait on them before doing builds. this risks running builds when the IDK or batch tests could fail. It also unrisks spending an extra five minutes in CI waiting for the last "test" phase thing to run in a long dependency chain, which is potentially more significant. Make IDK tests run for changes to idk, client, or batch directories, because at least one IDK thing uses the batch importer. Also, make that actually work, we think -- verified that the IDK tests got run when there were changes in that directory, but there aren't any now, so we don't expect to see them. Also, move the "IDK changed" rules into their own heading and incorporate them by reference, and simplify the conditional because it seemed to be Acting Up, but also make it check against refs/heads/master, rather than possibly just the parent commit, since that seems to be more consistent. Finally, we combine four of the tests (go tests, go tests future, go tests future plg, go tests shardwidth22) into two tests, both using the "future" compiler, one for plg, one for shardwidth22, so we don't need as many parallel runners and are less likely to end up waiting on them. At this point, the largest delay in CI is the chain through building lattice, which blocks some tasks for a fairly long time because they just have to wait for us to have built a container we can use as the server container in tests that need a server to work against. |
||
|---|---|---|
| .. | ||
| .gitlab-ci.yml | ||
| .perf-able-gitlab-ci.yml | ||
| batch-ci.yml | ||
| Dockerfile | ||