@deactivateduser60718 I am slowing down for Christmas. I will post a report and a couple of comments about CI status today. I think we should meet at the start of 2020. Maybe try to find a time we can all make it. As far as I understand, we are 4 people interested @samth, @deactivateduser60718 @notjack and myself.
I should apologize for the delay on this report. I got delayed with sending it to @notjack, which meant he was on holidays by then and could only review it afterwards.
At the same time I had promised I would go through him before publishing it online.
I have learned a few new things since then. The most unfortunate of all is that yaml anchors are not yet supported.
This means a lot of duplicated information in the yaml files - which made me wonder in a devious sort of way if we should have a #lang ci and compile this to yml just as we compile <http://configure.ac\|configure.ac> to a configure file. However this is work I cannot take at the moment.
I am hoping the GitHub guys are working on Yaml anchors…
I am close to porting all tests to Actions - mostly only those in gitlab are missing but I hope to get this done before the end of the year.
After that we should probably chat what’s next.
The dashboard would be a great thing and if @deactivateduser60718 and others want to have a go at it, it would be great.
But if you prefer to work on the ci job description let me know and we can share work porting gitlab jobs.
The dashboard could start as an experiment where we only store for each build configuration and host platform the build time.
I can register curl commands on the ci side to send this information to the dashboard and see how it goes.
This is something I will definitely not look at before everything else is done but would be happy for someone else to take the lead here and I sync on the job side.
Another topic is the oss-fuzz stuff - also feel free to have a go at it if you are keen on C development and racket internals - going hardcore if you try to do this for RacketCS which would be the goal.