Commit graph

7 commits

Author SHA1 Message Date
Alexander Artemenko
cb334f930e Fix :HOME path component issue.
First, we need to ensure that any errors in quicklisp fix loader cause failure of our own tests.
2024-04-15 18:08:08 +03:00
Alexander Artemenko
397c5328a9 Disabled test for allegro. 2024-02-25 13:55:01 +00:00
Alexander Artemenko
487d54503a Fixed calling of test.ros under the windows, simplified Roswell install and dont pollute PATH with a path to Action directory. 2024-01-30 19:02:51 +03:00
Alexander Artemenko
b7a3e0ed16 Added a test to check if need lisp really was installed and activated. 2024-01-27 22:11:03 +03:00
Matteo Landi
b615572a53 Try to make it easier to use this action
1. Move the `uses` for `setup-msys2/setup-msys2` inside our action.
   Note, composite actions do not support conditional steps yet, and to
   workaround that I had to fork setup-msys2 and suppress the error when
   run on Linux or Mac OS
2. `bash-or-msys2` got renamed to `lispsh`, this way workflows can
   simply refer to that when in need to use Lisp-related tools like
   `ros`, or `qlot`

PS. The tests workflow was updated to reflect the above mentioned tests.
2021-10-27 09:30:33 +02:00
Matteo Landi
f178435a8a Change workflow to _use_ the action the defined in the current commit 2021-10-26 19:21:58 +02:00
Matteo Landi
0b4f0353dd Add action workflow to facilitate testing
What:

- On Linux, MacOS, and Windows, installs sbcl-bin and all the _working_
  versions of Roswell, ASDF, and Qlot
- Runs `qlot exec ros` to install a project (to see if it errors out or
  not)

When:

- Each pushed change
- Each pull request action (not our own!)
- Every Saturday night

(Note: when running on the Saturday night, the workflow will try and
install the _latest_ version of Roswell, ASDF, and Qlot)
2021-10-26 18:09:38 +02:00