|
| 1 | +# This is a basic workflow to help you get started with Actions |
| 2 | + |
| 3 | +name: CI |
| 4 | + |
| 5 | +# Controls when the workflow will run |
| 6 | +on: |
| 7 | + # Triggers the workflow on push or pull request events but only for the develop branch |
| 8 | + push: |
| 9 | + branches-ignore: [ feature_systemverilog ] |
| 10 | + pull_request: |
| 11 | + branches-ignore: [ feature_systemverilog ] |
| 12 | + |
| 13 | + # Allows you to run this workflow manually from the Actions tab |
| 14 | + workflow_dispatch: |
| 15 | + |
| 16 | +# A workflow run is made up of one or more jobs that can run sequentially or in parallel |
| 17 | +jobs: |
| 18 | + # This workflow contains a single job called "build" |
| 19 | + build: |
| 20 | + # The type of runner that the job will run on |
| 21 | + runs-on: ubuntu-latest |
| 22 | + strategy: |
| 23 | + matrix: |
| 24 | + python-version: [3.7, 3.8, 3.9] |
| 25 | + |
| 26 | + # Steps represent a sequence of tasks that will be executed as part of the job |
| 27 | + steps: |
| 28 | + # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it |
| 29 | + - uses: actions/checkout@v2 |
| 30 | + # Setup Python |
| 31 | + - name: Set up Python ${{ matrix.python-version }} |
| 32 | + uses: actions/setup-python@v2 |
| 33 | + with: |
| 34 | + python-version: ${{ matrix.python-version }} |
| 35 | + # Install apt dependencies |
| 36 | + - name: Install apt dependencies |
| 37 | + run: apt install iverilog verilator |
| 38 | + # Install dependencies |
| 39 | + - name: Install dependencies |
| 40 | + run: | |
| 41 | + python -m pip install --upgrade pip |
| 42 | + pip install pytest pytest-pythonpath jinja2 pyverilog numpy |
| 43 | + # Run pytest |
| 44 | + - name: Test with pytest |
| 45 | + run: | |
| 46 | + python -m pytest tests examples |
0 commit comments