paku/setup-lisp
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity
setup-lisp/.github/workflows/tests.yml

91 lines
2.8 KiB
YAML
Raw Normal View History

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 15:18:30 +00:00
name: tests
on:
push:
Added a test to check if need lisp really was installed and activated.
2024-01-26 14:39:24 +00:00
branches:
- master
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 15:18:30 +00:00
pull_request:
schedule:
- cron: "0 0 * * SUN"
jobs:
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 05:16:26 +00:00
tests:
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 15:18:30 +00:00
strategy:
fail-fast: false # Let the workflow continue as much as possible
matrix:
include:
- os: ubuntu-latest
Added a test to check if need lisp really was installed and activated.
2024-01-26 14:39:24 +00:00
lisp: sbcl
# Just to ensure test.ros will not fail when version
# is specified explicitly
- os: ubuntu-latest
lisp: sbcl/2.3.1
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 15:18:30 +00:00
- os: macos-latest
lisp: sbcl-bin
- os: windows-latest
lisp: sbcl-bin
Added a test to check if need lisp really was installed and activated.
2024-01-26 14:39:24 +00:00
- os: ubuntu-latest
lisp: sbcl-bin
- os: ubuntu-latest
lisp: ccl-bin
- os: ubuntu-latest
lisp: clisp-head
- os: ubuntu-latest
lisp: ecl
- os: ubuntu-latest
lisp: abcl-bin
- os: ubuntu-latest
lisp: clasp-bin
- os: ubuntu-latest
lisp: cmu-bin
Fixed calling of test.ros under the windows, simplified Roswell install and dont pollute PATH with a path to Action directory.
2024-01-28 05:52:52 +00:00
Disabled test for allegro.
2024-02-25 13:55:01 +00:00
# See issue: https://github.com/40ants/setup-lisp/issues/22
# - os: ubuntu-latest
# lisp: allegro
Fixed calling of test.ros under the windows, simplified Roswell install and dont pollute PATH with a path to Action directory.
2024-01-28 05:52:52 +00:00
# See issue: https://github.com/40ants/setup-lisp/issues/15
# - os: ubuntu-latest
# lisp: clisp
# See issue: https://github.com/40ants/setup-lisp/issues/16
# - os: ubuntu-latest
# lisp: clasp
Added a test to check if need lisp really was installed and activated.
2024-01-26 14:39:24 +00:00
# See issue: https://github.com/40ants/setup-lisp/issues/17
# - os: ubuntu-latest
# lisp: mkcl
# See issue: https://github.com/40ants/setup-lisp/issues/18
# - os: ubuntu-latest
# lisp: npt
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 15:18:30 +00:00
defaults:
run:
Fixed calling of test.ros under the windows, simplified Roswell install and dont pollute PATH with a path to Action directory.
2024-01-28 05:52:52 +00:00
shell: lispsh -eo pipefail {0}
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 15:18:30 +00:00
env:
LISP: ${{ matrix.lisp }}
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 05:16:26 +00:00
name: test with ${{ matrix.lisp }} on ${{ matrix.os }}
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 15:18:30 +00:00
runs-on: ${{ matrix.os }}
Added a test to check if need lisp really was installed and activated.
2024-01-26 14:39:24 +00:00
timeout-minutes: 10
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 15:18:30 +00:00
steps:
Fixed calling of test.ros under the windows, simplified Roswell install and dont pollute PATH with a path to Action directory.
2024-01-28 05:52:52 +00:00
- uses: actions/checkout@v4
Change workflow to _use_ the action the defined in the current commit
2021-10-26 16:19:12 +00:00
with:
# The repo already contains the qlot and qlot.lock files, and since
# we don't want those to interfere with the current test run, we
# clone the repository somewhere else (i.e. something different from
# the default './')
Fixed calling of test.ros under the windows, simplified Roswell install and dont pollute PATH with a path to Action directory.
2024-01-28 05:52:52 +00:00
path: setup-lisp
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 15:18:30 +00:00
- name: Call setup-lisp with default arguments
if: github.event_name != 'schedule'
Change workflow to _use_ the action the defined in the current commit
2021-10-26 16:19:12 +00:00
uses: ./setup-lisp/
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 15:18:30 +00:00
- name: Call setup-lisp and install latest
if: github.event_name == 'schedule'
Change workflow to _use_ the action the defined in the current commit
2021-10-26 16:19:12 +00:00
uses: ./setup-lisp/
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 15:18:30 +00:00
with:
roswell-version: latest
# XXX remove this override (i.e. put "latest" back in) after the
# following roswell issue has been solved:
# https://github.com/roswell/roswell/issues/497
asdf-version: 3.3.5.3
qlot-version: latest
Fixed calling of test.ros under the windows, simplified Roswell install and dont pollute PATH with a path to Action directory.
2024-01-28 05:52:52 +00:00
- run: which ros
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 05:16:26 +00:00
- run: ros config
Added a test to check if need lisp really was installed and activated.
2024-01-26 14:39:24 +00:00
- run: qlot exec ros install 40ants/cl-info
- run: qlot exec cl-info
Reference in a new issue Copy permalink