Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

One of the rebal-throttle tests uses the wrong variable #2315

Closed
jamielinux opened this issue Apr 7, 2021 · 0 comments · Fixed by #2316
Closed

One of the rebal-throttle tests uses the wrong variable #2315

jamielinux opened this issue Apr 7, 2021 · 0 comments · Fixed by #2316

Comments

@jamielinux
Copy link
Contributor

Description of problem:

Test specifies THORTTLE_LEVEL on line 47, then uses THROTTLE_LEVEL on line 49.

#Setting thorttle number to be more than the number of cores should fail
THORTTLE_LEVEL=$((cores+1))
TEST echo $THORTTLE_LEVEL
EXPECT "failed" set_throttle $THROTTLE_LEVEL
EXPECT "$cores" echo `$CLI volume info | grep rebal-throttle | awk '{print $2}'`

amarts pushed a commit that referenced this issue Apr 8, 2021
The final test doesn't test what it means to test. It still fails as
expected, but only because at this point `THROTTLE_LEVEL` is still set
to `garbage`.

Easily fixed by correcting the typos in the variable names, and thus
fixes #2315

Signed-off-by: Jamie Nguyen <j@jamielinux.com>
chenglin130 pushed a commit to chenglin130/glusterfs that referenced this issue Apr 13, 2021
The final test doesn't test what it means to test. It still fails as
expected, but only because at this point `THROTTLE_LEVEL` is still set
to `garbage`.

Easily fixed by correcting the typos in the variable names, and thus
fixes gluster#2315

Signed-off-by: Jamie Nguyen <j@jamielinux.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant