Skip to content

Commit 065886b

Browse files
committed
sysbench: fix typos
Minor typos found. pre-commit run codespell --files workflows/sysbench/Kconfig* codespell................................................................Passed Signed-off-by: Daniel Gomez <[email protected]>
1 parent bd77f68 commit 065886b

File tree

3 files changed

+8
-8
lines changed

3 files changed

+8
-8
lines changed

workflows/sysbench/Kconfig

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ config SYSBENCH_MYSQL_INNOODB_REDO_LOG_CAPACITY
4040
help
4141
innodb_dedicated_server=ON is not compatible with innodb_flush_method=O_DIRECT
4242
and so we do what we can. See the following values which MySQL does
43-
recommand use when dedicated server is enabled, we just have to compute
43+
recommend use when dedicated server is enabled, we just have to compute
4444
on our own and test on our own:
4545

4646
https://dev.mysql.com/doc/refman/8.0/en/innodb-dedicated-server.html

workflows/sysbench/Kconfig.docker

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ config SYSBENCH_MYSQL_CONTAINER_NAME
4040
Set the name for the MySQL Docker container.
4141

4242
config SYSBENCH_MYSQL_CONTAINER_PYTHON_PATH
43-
string "The MySQL container pytyhon path"
43+
string "The MySQL container python path"
4444
default "/usr/local/lib/python3.9/site-packages" if SYSBENCH_MYSQL_CONTAINER_IMAGE_8_0
4545
output yaml
4646
help
@@ -60,7 +60,7 @@ config SYSBENCH_MYSQL_CONTAINER_HOST_CLIENT_CONFIG_PATH
6060
us make edits on the node.
6161

6262
config SYSBENCH_MYSQL_CONTAINER_CLIENT_CONFIG
63-
string "The MySQL container client configuraton file"
63+
string "The MySQL container client configuration file"
6464
default "/root/.my.cnf"
6565
output yaml
6666
help
@@ -101,7 +101,7 @@ config SYSBENCH_MYSQL_CONTAINER_HOST_ROOT_PATH
101101
When using a container, in order to support telemetry we rely on
102102
a mysqlsh plugin which we git clone on the node where we will
103103
run the container on. We use a container volume to let the container
104-
get access to this clone. This specificies the path on the node which
104+
get access to this clone. This specifies the path on the node which
105105
we will use a docker volume passed onto the container as the
106106
/root/ directory.
107107

@@ -145,4 +145,4 @@ config SYSBENCH_DOCKER_TELEMETRY_PATH
145145
default SYSBENCH_TELEMETRY_PATH
146146
output yaml
147147
help
148-
Where to place telemetry informaton inside the docker container.
148+
Where to place telemetry information inside the docker container.

workflows/sysbench/Kconfig.fs

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,12 +7,12 @@ config SYSBENCH_TEST_ATOMICS
77
output yaml
88
select KDEVOPS_BASELINE_AND_DEV
99
help
10-
This type of test is aimed of testing the emperical value of support
10+
This type of test is aimed of testing the empirical value of support
1111
for large atomics on storage devices and its impact on databases.
12-
Most drives today support only power-fail safe gaurantees when writing
12+
Most drives today support only power-fail safe guarantees when writing
1313
up to 4 KiB. Drives which support 16 KiB atomic writes or larger can
1414
take advanage of software features in databases which typically
15-
do software work arounds to gaurantee writes above 4 KiB will be
15+
do software work arounds to guarantee writes above 4 KiB will be
1616
recoverable in case of power failure.
1717

1818
Different database have different features one can disable if one has

0 commit comments

Comments
 (0)