> Also, I agree about simplifying macOS build if it will help while we get to q > better situation.
We can have a special test list for macOS that includes just a few configs from the simulator and other chips. > There has been some talk about supporting non hosted runners, but there are some security issues that still need to be worked out. > The problem is that rolling our own can be quite a pain to maintain IMHO (unless someone has access to some powerful high-availabilty spare machine). We would also have to redo all CI handling since it wouldn't be GitHub's. How about runners hosted and maintained by another organisation? Is this something that we can have? This could include runners with "targets" where we can do functional tests in hardware instead of the simulator or QEMU. On Wed, Mar 31, 2021 at 3:05 PM Matias N. <mat...@imap.cc> wrote: > > Then situation is a bit better now, since we did not continue to submit as > many Para. However, the builds are still lagging (there are ones from 20hr > ago running). I see many of the new "cancelling duplicates" jobs queued but > they have not yet run. > I have cancelled a few myself. In case I cancelled a running one by mistake, > please apologize. I would suggest we give the system a while to catch up. > > In the meantime, if you are force pushing a PR, please rebase first. > > Also, I agree about simplifying macOS build if it will help while we get to q > better situation. > > Best, > Matias
