name: SITL Tests

on: [push]

jobs:
  build:
    runs-on: ubuntu-latest
    container: px4io/px4-dev-simulation-bionic:2019-12-18
    steps:
    - uses: actions/checkout@v1
    - name: Set Python 3 as default
      run: update-alternatives --install /usr/bin/python python /usr/bin/python3 10
    - name: Install psutil
      run: pip3 install psutil
    - name: Build PX4 in SITL integration test mode
      # Build all targets
      run: DONT_RUN=1 make px4_sitl gazebo mavsdk_tests
    - name: Run simulation tests
      # Grind configuration: Run ~8 minutes for 35 iterations == close to the 6 hour limit of Github Actions
      run:  test/mavsdk_tests/mavsdk_test_runner.py --speed-factor 20 --iterations 1 --fail-early

name: SITL Tests

on: [push]

jobs:
  build:
    runs-on: ubuntu-latest
    container: px4io/px4-dev-simulation-bionic:2019-12-18
    steps:
    - uses: actions/checkout@v1
      with:
        token: ${{ secrets.ACCESS_TOKEN }}
        submodules: true
    - name: Set Python 3 as default
      run: update-alternatives --install /usr/bin/python python /usr/bin/python3 10
    - name: Install psutil
      run: pip3 install psutil
    - name: Build PX4 in SITL integration test mode
      # Build all targets
      run: DONT_RUN=1 make px4_sitl gazebo mavsdk_tests
    - name: Run simulation tests
      # Grind configuration: Run ~8 minutes for 35 iterations == close to the 6 hour limit of Github Actions
      run:  test/mavsdk_tests/mavsdk_test_runner.py --speed-factor 20 --iterations 1 --fail-early

Add access token to SITL test Github Action
Add access token to SITL test Github Action

This is needed for downstream adopters. We want them to re-use our CI tests so that contributions already are pre-tested when they are submitted.