On Oct 16, 2020, at 20:13, Eric Timmons etimmons@mit.edu wrote:
"Robert Goldman" rpgoldman@sift.info writes:
In mine, I simply set the environment variables `ASDF_TEST_LISPS` and the variables that point to the lisp implementations. Then I call `make test-all-no-upgrades-no-stop`.
Just to clarify, it sounds from this that you don't actually care if the upgrade tests are run? Do you ever want to run them via CI? As it currently stands they're the slowest jobs, so finding some way to reduce the number of times they're run would be a win.
Some tests are better than no tests.
The CLF advocates a merge of [!146][] as we then we can adjust runners as needed for capacity and capability. The default runners are Linux. Eric Timmons is setting up a macOS runner which can be used. Windows runners are further in the future.
Among other positive attributes, this establishes a [non-dotfile artifact][file:ci-gitlab.yml] which runs the CI sequence, so is ammendable to further pull requests.
For commercial implementations, we are still working out the details that would be conformant with the licensing conditions.
[!144]: https://gitlab.common-lisp.net/asdf/asdf/-/merge_requests/146
[file:ci-gitlab.yml]: https://gitlab.common-lisp.net/asdf/asdf/-/blob/5a15171a44310fbf3ded80a93b4b7b6bdccaf04f/gitlab-ci.yml