R_CMD_CHECK runs very slow in MacOS latest

[cnluzon]

Latest tests added made Check step in MacOS very slow (took 24 minutes full run whereas Ubuntu runs in 11).

My guess is that it has something to do with bw_bins that was untested before for efficiency.

I can either skip the bw_bins test for certain cases if they slow down this, and approach the testing of these functions through mocking and testing the underlying functions.

Note that this also affects regular installation time in MacOS, most likely.

[cnluzon]

Further investigation into this shows that it's not the tests, but some accumulation on things that run slower on MacOS, apparently, which are BioConductor installation (4min vs 8min) and the whole R_CMD_CHECK step list being slightly slower in each step, accumulating to ~11minutes vs 4 minutes in Ubuntu.

I am not sure how easy it is to fix this. It slows down the merging of pull requests, though.

[cnluzon]

This seems to depend on other external factors. Now, including quite a bit more testing, times are again around 10 minutes and it is evenly distributed across Windows, Ubuntu and MacOS, so I am going to close this for now.

[cnluzon]

Reopening this because it takes way too long.

Sometimes there is some kind of timeout crash when there are no nodes available for running. This seems to happen more often with MacOS nodes.

One option is to run Ubuntu only at this time since it caches package installing and it will still allow me to catch R-CMD-Check fails (automated tests, installation to some degree and documentation warnings). If ran into other type of problems (installation and so on) I can reinstate the testing for several platforms.