upstream/haproxy
1
0
Fork 0
mirror of https://github.com/haproxy/haproxy.git synced 2026-06-08 16:23:24 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 4
haproxy/reg-tests/stats/stats-file.vtc

45 lines
918 B
Text
Raw Permalink Normal View History

REGTESTS: stats: add test stats-file counters preload Define a simple regtest to check stats-file loading on startup. A sample stats-file is written with some invalid values which should be silently ignored.
2024-05-02 09:25:53 -04:00
varnishtest "Preload counters via stats-file"
REGTESTS: replace REQUIRE_VERSION by version_atleast REQUIRE_VERSION usage is deprecated in regtests for version >= 2.5. This allows to specify full correct 3.0-dev9 version.
2024-05-03 10:32:30 -04:00
feature cmd "$HAPROXY_PROGRAM -cc 'version_atleast(3.0-dev9)'"
REGTESTS: stats: add test stats-file counters preload Define a simple regtest to check stats-file loading on startup. A sample stats-file is written with some invalid values which should be silently ignored.
2024-05-02 09:25:53 -04:00
feature ignore_unknown_macro
haproxy h1 -conf {
global
REGTESTS: restrict execution to a single thread group When threads are enabled and running on a machine with multiple CCX or multiple nodes, thread groups are now enabled since 3.3-dev2, causing load-balancing algorithms to randomly fail due to incoming connections spreading over multiple groups and using different load balancing indexes. Let's just force "thread-groups 1" into all configs when threads are enabled to avoid this.
2025-06-30 12:44:07 -04:00
.if feature(THREAD)
thread-groups 1
.endif
REGTESTS: stats: add test stats-file counters preload Define a simple regtest to check stats-file loading on startup. A sample stats-file is written with some invalid values which should be silently ignored.
2024-05-02 09:25:53 -04:00
stats-file ${testdir}/sample-stats-file
REGTESTS: add missing timeouts to 30 tests No less than 30 tests were missing timeouts, preventing them from being started with zero-warning. Since they were not supposed to trigger, they have been set to 30s so as never to trigger, and now they do not produce any warning anymore.
2024-11-19 01:43:04 -05:00
defaults
timeout client 30s
timeout server 30s
timeout connect 30s
REGTESTS: stats: add test stats-file counters preload Define a simple regtest to check stats-file loading on startup. A sample stats-file is written with some invalid values which should be silently ignored.
2024-05-02 09:25:53 -04:00
frontend fe
guid guid-fe
bind "fd@${feS}" guid-prefix guid-feS
frontend fe2
guid guid-fe2
option socket-stats
bind "fd@${fe2S}" guid-prefix guid-fe2S
backend be
guid guid-be
server srv ${s1_addr}:${s1_port} guid guid-srv
} -start
haproxy h1 -cli {
send "show stat fe 15 -1 typed"
MEDIUM: stats: add persistent state to typed output format Add a fourth character to the second column of the "typed output format" to indicate whether the value results from a volatile or persistent metric ('V' or 'P' characters respectively). A persistent metric means the value could possibily be preserved across reloads by leveraging a shared memory between multiple co-processes. Such metrics are identified as "shared" in the code (since they are possibly shared between multiple co-processes) Some reg-tests were updated to take that change into account, also, some outputs in the configuration manual were updated to reflect current behavior.
2025-04-15 05:49:42 -04:00
expect ~ "F.*.*.*.stot.1:MCP.*:u64:1024"
REGTESTS: stats: add test stats-file counters preload Define a simple regtest to check stats-file loading on startup. A sample stats-file is written with some invalid values which should be silently ignored.
2024-05-02 09:25:53 -04:00
send "show stat fe2 15 -1 typed"
MEDIUM: stats: add persistent state to typed output format Add a fourth character to the second column of the "typed output format" to indicate whether the value results from a volatile or persistent metric ('V' or 'P' characters respectively). A persistent metric means the value could possibily be preserved across reloads by leveraging a shared memory between multiple co-processes. Such metrics are identified as "shared" in the code (since they are possibly shared between multiple co-processes) Some reg-tests were updated to take that change into account, also, some outputs in the configuration manual were updated to reflect current behavior.
2025-04-15 05:49:42 -04:00
expect ~ "L.*.*.*.stot.1:MCP.*:u64:1024"
REGTESTS: stats: add test stats-file counters preload Define a simple regtest to check stats-file loading on startup. A sample stats-file is written with some invalid values which should be silently ignored.
2024-05-02 09:25:53 -04:00
send "show stat be 15 -1 typed"
MEDIUM: stats: add persistent state to typed output format Add a fourth character to the second column of the "typed output format" to indicate whether the value results from a volatile or persistent metric ('V' or 'P' characters respectively). A persistent metric means the value could possibily be preserved across reloads by leveraging a shared memory between multiple co-processes. Such metrics are identified as "shared" in the code (since they are possibly shared between multiple co-processes) Some reg-tests were updated to take that change into account, also, some outputs in the configuration manual were updated to reflect current behavior.
2025-04-15 05:49:42 -04:00
expect ~ "B.*.*.*.stot.1:MCP.*:u64:1024"
REGTESTS: stats: add test stats-file counters preload Define a simple regtest to check stats-file loading on startup. A sample stats-file is written with some invalid values which should be silently ignored.
2024-05-02 09:25:53 -04:00
send "show stat be 15 -1 typed"
MEDIUM: stats: add persistent state to typed output format Add a fourth character to the second column of the "typed output format" to indicate whether the value results from a volatile or persistent metric ('V' or 'P' characters respectively). A persistent metric means the value could possibily be preserved across reloads by leveraging a shared memory between multiple co-processes. Such metrics are identified as "shared" in the code (since they are possibly shared between multiple co-processes) Some reg-tests were updated to take that change into account, also, some outputs in the configuration manual were updated to reflect current behavior.
2025-04-15 05:49:42 -04:00
expect ~ "S.*.*.*.stot.1:MCP.*:u64:1024"
REGTESTS: stats: add test stats-file counters preload Define a simple regtest to check stats-file loading on startup. A sample stats-file is written with some invalid values which should be silently ignored.
2024-05-02 09:25:53 -04:00
}
Reference in a new issue Copy permalink