Only run bootstrapped tests for the Windows CI

[smarter]

They are a superset of the non-bootstrapped tests and bootstrapping
issues should be caught by the non-bootstrapped Linux runner.

[liufengyun]

LGTM

[michelou]

Another alternative : use more than 1 workflow file.

• See https://stackoverflow.com/questions/57115520/can-i-have-multiple-github-actions-workflow-files
• Limit is 20 workflow files (if I remember correctly)

For instance (assuming an appropriate workflow filter) :

• ci.yaml (linux) and
• ci-win.yaml (environment variable ImageOS is win16 or win19).

Yet another alternative would be to use one of the github.event properties to choose between the above workflow files (e.g. a push message containing the word "windows" would fire ci-win.yaml).

[michelou]

@smarter @liufengyun Here I'd like to emphasize the fact that the job test_boostrapped is not strictly a superset of test since bootstrapCmdTests (called at the end of the 1st job) is different from cmdTests (called in the 2nd job).

[smarter]

I don't think the windows CI runs either of those anyway because they're bash scripts, but it'd be nice if it did indeed.

[michelou]

@smarter As a reminder I'm running both batch files cmdTests and bootstrapCmdTests for over 2 years (at least since Dotty 0.7, yes Dotty 0.7) locally on my Win10 laptop (see description in BUILD.md).
If you check again the email I sent you in CC on October 16, 2020 (09h19), you will see the two batch files been executed in my GitHub Actions, for instance the run of October 15.