Unverified Commit c913be04 authored by Salvatore Sanfilippo's avatar Salvatore Sanfilippo Committed by GitHub
Browse files

Merge pull request #6932 from oranagra/fix_defrag_latency_test

fix github actions failing latency test for active defrag
parents 319a6831 53789342
...@@ -3,11 +3,8 @@ name: CI ...@@ -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: ...@@ -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
test-ubuntu-old:
runs-on: ubuntu-16.04
steps:
- uses: actions/checkout@v1
- name: make
run: make
build-macos-latest: build-macos-latest:
strategy: runs-on: macos-latest
matrix:
platform: [macos-latest, macOS-10.14]
runs-on: ${{ matrix.platform }}
steps: steps:
- uses: actions/checkout@v1 - uses: actions/checkout@v1
- name: make - name: make
......
...@@ -100,7 +100,7 @@ start_server {tags {"defrag"}} { ...@@ -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"}} { ...@@ -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"}} { ...@@ -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]
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment