ci issueshttps://gitlab.rts.mpi-sws.org/iris/ci/-/issues2021-05-20T11:59:17Zhttps://gitlab.rts.mpi-sws.org/iris/ci/-/issues/2Introduce some kind of pre-merge gating on CI2021-05-20T11:59:17ZRalf Jungjung@mpi-sws.orgIntroduce some kind of pre-merge gating on CIIt would be great to adapt the ["not rocket science"](https://graydon2.dreamwidth.org/1597.html) principle for at least some of our repositories. That means that we would set things up such that CI runs *before* anything enters the maste...It would be great to adapt the ["not rocket science"](https://graydon2.dreamwidth.org/1597.html) principle for at least some of our repositories. That means that we would set things up such that CI runs *before* anything enters the master branch.
Right now, on GitLab this requires an external bot, such as [marge-bot](https://github.com/smarkets/marge-bot).https://gitlab.rts.mpi-sws.org/iris/ci/-/issues/1Gather per-statement timing data2022-03-02T06:38:45ZRalf Jungjung@mpi-sws.orgGather per-statement timing dataMany have requested it, most recently @janno -- it would be great if we could gather per-statement timing data on CI.Many have requested it, most recently @janno -- it would be great if we could gather per-statement timing data on CI.