zhuyijun/read-redis
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix github actions failing latency test for active defrag

Browse Source 
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
This commit is contained in:
Oran Agra 2020-02-25 13:01:52 +02:00
parent 319a6831a9
commit 537893420b
2 changed files with 15 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
.github/workflows/ci.yml vendored
View File

@ -3,11 +3,8 @@ name: CI
on: [push, pull_request] on: [push, pull_request]
jobs: jobs:
build-ubuntu: test-ubuntu-latest:
strategy: runs-on: ubuntu-latest
matrix:
platform: [ubuntu-latest, ubuntu-16.04]
runs-on: ${{ matrix.platform }}
steps: steps:
- uses: actions/checkout@v1 - uses: actions/checkout@v1
- name: make - name: make
@ -15,13 +12,17 @@ jobs:
- name: test - name: test
run: | run: |
sudo apt-get install tcl8.5 sudo apt-get install tcl8.5
make test ./runtest --clients 1 --verbose
build-macos-latest: test-ubuntu-old:
strategy: runs-on: ubuntu-16.04
matrix: steps:
platform: [macos-latest, macOS-10.14] - uses: actions/checkout@v1
runs-on: ${{ matrix.platform }} - name: make
run: make
build-macos-latest:
runs-on: macos-latest
steps: steps:
- uses: actions/checkout@v1 - uses: actions/checkout@v1
- name: make - name: make

6
tests/unit/memefficiency.tcl
View File

@ -100,7 +100,7 @@ start_server {tags {"defrag"}} {
assert {$frag < 1.1} assert {$frag < 1.1}
# due to high fragmentation, 100hz, and active-defrag-cycle-max set to 75, # due to high fragmentation, 100hz, and active-defrag-cycle-max set to 75,
# we expect max latency to be not much higher than 7.5ms but due to rare slowness threshold is set higher # we expect max latency to be not much higher than 7.5ms but due to rare slowness threshold is set higher
assert {$max_latency <= 60} assert {$max_latency <= 30}
} else { } else {
set _ "" set _ ""
} }
@ -226,7 +226,7 @@ start_server {tags {"defrag"}} {
assert {$frag < 1.1} assert {$frag < 1.1}
# due to high fragmentation, 100hz, and active-defrag-cycle-max set to 75, # due to high fragmentation, 100hz, and active-defrag-cycle-max set to 75,
# we expect max latency to be not much higher than 7.5ms but due to rare slowness threshold is set higher # we expect max latency to be not much higher than 7.5ms but due to rare slowness threshold is set higher
assert {$max_latency <= 60} assert {$max_latency <= 30}
} }
# verify the data isn't corrupted or changed # verify the data isn't corrupted or changed
set newdigest [r debug digest] set newdigest [r debug digest]
@ -317,7 +317,7 @@ start_server {tags {"defrag"}} {
assert {$frag < 1.1} assert {$frag < 1.1}
# due to high fragmentation, 100hz, and active-defrag-cycle-max set to 75, # due to high fragmentation, 100hz, and active-defrag-cycle-max set to 75,
# we expect max latency to be not much higher than 7.5ms but due to rare slowness threshold is set higher # we expect max latency to be not much higher than 7.5ms but due to rare slowness threshold is set higher
assert {$max_latency <= 60} assert {$max_latency <= 30}
} }
# verify the data isn't corrupted or changed # verify the data isn't corrupted or changed
set newdigest [r debug digest] set newdigest [r debug digest]