You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2 things I noticed when working on adding check for cctest.tap failures in CI. We distribute the test cases in 4 groups (%RUN_SUBSET%) and each machine runs individual group. However all the groups run cctest and build the addons. Although not trivial, we can speed up the test job by running cctest on just 1 machine (need to figure out how) and also skip building addons if that group won't be testing test-addons or test-addons-napi unless there was historical reason for not doing it in this way.
Let's leave this open. The Windows jobs will have to be updated to pipelines some time (I plan to do it when I find the time), this is a nice feature to include in that effort.
Activity
rvagg commentedon Jul 21, 2017
this is certainly a job for @joaocgreis, he's our multi-job master, the rest of us just 🙈
maclover7 commentedon Feb 13, 2018
ping @kunalspathak
joaocgreis commentedon Feb 13, 2018
Let's leave this open. The Windows jobs will have to be updated to pipelines some time (I plan to do it when I find the time), this is a nice feature to include in that effort.
joaocgreis commentedon Dec 18, 2019
This has been done for some time, and now included in #2099.