redict/.github/workflows/ci.yml

name: CI

on: [push, pull_request]

jobs:
  test-ubuntu-latest:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v1
    - name: make
      run: make
    - name: test
      run: |
        sudo apt-get install tcl8.5
        ./runtest --clients 2 --verbose

  build-ubuntu-old:
    runs-on: ubuntu-16.04
    steps:
    - uses: actions/checkout@v1
    - name: make
      run: make

  build-macos-latest:
    runs-on: macos-latest
    steps:
    - uses: actions/checkout@v1
    - name: make
      run: make
add CI action 2019-10-20 03:04:25 -04:00			`name: CI`

			`on: [push, pull_request]`

			`jobs:`
fix github actions failing latency test for active defrag seems that github actions are slow, using just one client to reduce false positives. also adding verbose, testing only on latest ubuntu, and building on older one. when doing that, i can reduce the test threshold back to something saner 2020-02-25 06:01:52 -05:00			`test-ubuntu-latest:`
			`runs-on: ubuntu-latest`
add CI action 2019-10-20 03:04:25 -04:00			`steps:`
			`- uses: actions/checkout@v1`
			`- name: make`
			`run: make`
			`- name: test`
			`run: \|`
			`sudo apt-get install tcl8.5`
fix github actions failing latency test for active defrag - part 2 it seems that running two clients at a time is ok too, resuces action time from 20 minutes to 10. we'll use this for now, and if one day it won't be enough we'll have to run just the sensitive tests one by one separately from the others. this commit also fixes an issue with the defrag test that appears to be very rare. 2020-02-26 01:12:07 -05:00			`./runtest --clients 2 --verbose`
fix github actions failing latency test for active defrag seems that github actions are slow, using just one client to reduce false positives. also adding verbose, testing only on latest ubuntu, and building on older one. when doing that, i can reduce the test threshold back to something saner 2020-02-25 06:01:52 -05:00
fix github actions failing latency test for active defrag - part 2 it seems that running two clients at a time is ok too, resuces action time from 20 minutes to 10. we'll use this for now, and if one day it won't be enough we'll have to run just the sensitive tests one by one separately from the others. this commit also fixes an issue with the defrag test that appears to be very rare. 2020-02-26 01:12:07 -05:00			`build-ubuntu-old:`
fix github actions failing latency test for active defrag seems that github actions are slow, using just one client to reduce false positives. also adding verbose, testing only on latest ubuntu, and building on older one. when doing that, i can reduce the test threshold back to something saner 2020-02-25 06:01:52 -05:00			`runs-on: ubuntu-16.04`
			`steps:`
			`- uses: actions/checkout@v1`
			`- name: make`
			`run: make`
add CI action 2019-10-20 03:04:25 -04:00
			`build-macos-latest:`
fix github actions failing latency test for active defrag seems that github actions are slow, using just one client to reduce false positives. also adding verbose, testing only on latest ubuntu, and building on older one. when doing that, i can reduce the test threshold back to something saner 2020-02-25 06:01:52 -05:00			`runs-on: macos-latest`
add CI action 2019-10-20 03:04:25 -04:00			`steps:`
			`- uses: actions/checkout@v1`
			`- name: make`
			`run: make`