proxysql

Commit Graph

Author	SHA1	Message	Date
Rene Cannao	ca409366cb	Address review feedback on TSDB tests - Use cl.admin_host instead of cl.host for admin HTTP endpoints - Don't log auth credentials (security issue) - Fail fast when prerequisite SET/LOAD commands fail - Assert on specific test_downsample_metric rows in hourly table	3 weeks ago
Rene Cannao	809878c253	Fix TSDB TAP tests for Docker-based CI test_tsdb_variables-t: - Add verbose logging for downsampling test - Insert test data with timestamps from 2 hours ago before downsampling - The TSDB downsample logic only processes completed hours, so we need historical data for the test to succeed - Add cleanup of test data after the test test_tsdb_api-t: - Use configurable host from environment (cl.host) instead of hardcoded 127.0.0.1 - Add verbose logging for configuration and test progress - Use proper authentication credentials from command line - Increase retries for dashboard endpoint - Add detailed error messages Fixes #5483	3 weeks ago
Rene Cannao	4dcabbc7ec	Move test_utf8mb4_as_ci-4841-t to mysql84-g1 group only This test requires MySQL 8.0+ for utf8mb4_0900_as_ci collation support. Removed from legacy-g4 and all g4 variants since they don't have MySQL 8.	3 weeks ago
Rene Cannao	186ce308c6	Fix test_sqlite3_pass_exts plan for MySQL version differences Move plan() call after MySQL version detection to set correct test count: - MySQL 8.0+: 2213 tests (includes BY RANDOM PASSWORD tests) - MySQL 5.7: 2012 tests (skips BY RANDOM PASSWORD tests) Previously the test always planned 2213 tests, causing TAP failures when running against MySQL 5.7 because only 2113 tests executed.	3 weeks ago
Rene Cannao	4a0300f844	Fix test_query_rules_routing for Docker-based CI - complete fix Two additional issues fixed: 1. Query hint hostgroup: ProxySQL query hints like /* ;hostgroup=0;... */ were hardcoded to hostgroup 0. Now dynamically replaced with the discovered writer hostgroup. 2. Also removed hardcoded TAP_MYSQLPASSWORD=root from test_sqlite3_pass_exts-t.env to allow infrastructure-provided password to be used.	3 weeks ago
Rene Cannao	e9a16550c6	Improve test_query_rules_routing hostgroup discovery - Query runtime_mysql_users instead of mysql_users for default_hostgroup - Use mysql_replication_hostgroups to find writer/reader hostgroup pairs - Fallback to runtime_mysql_servers if no replication hostgroups configured - Remove hardcoded TAP_MYSQLPASSWORD from test_sqlite3_pass_exts-t.env These changes allow tests to work correctly with Docker-based CI infrastructure where hostgroups may differ from hardcoded defaults.	3 weeks ago
Rene Cannao	f2db3cbb1e	Fix test_sqlite3_pass_exts for Docker-based CI infrastructure Remove hardcoded TAP_MYSQLPORT=14806 from test .env files to use the infrastructure-provided port (3306). The hardcoded port was causing connection failures when tests run inside Docker containers.	3 weeks ago
Rene Cannao	7bbda48f29	Fix test_query_rules_routing for Docker-based CI infrastructure - Add dynamic hostgroup discovery from mysql_servers table - Replace hardcoded hostgroups (0, 1) with discovered ones (e.g., 1300, 1301) - Add comprehensive debugging output for troubleshooting: - Current server and user configuration - Discovered hostgroups - Query execution details (before/after counts) - Routing failures with specific queries The test was failing because it used hardcoded hostgroups 0 and 1, but the Docker CI infrastructure uses dynamic hostgroups (1300, 1301, etc.) depending on the infrastructure type.	3 weeks ago
Rene Cannao	e3ccdb7d12	Fix test_load_from_config_validation for Docker-based CI - Use REGULAR_INFRA_DATADIR environment variable for config file path (falls back to /tmp for local mode) - Add initial diag messages describing test purpose - Add step-by-step debugging messages during test execution - Update file header comment with test description This fixes the issue where ProxySQL running in a Docker container couldn't access config files created in /tmp on the test runner host.	3 weeks ago
Rene Cannao	0bc75cd589	Fix test validation and coverage HTML generation - Fix false positive "missing tests" errors when processing secondary workdirs (e.g., deprecate_eof_support). The validation now only checks tests that actually exist in the current workdir rather than all tests in groups.json for the TAP_GROUP. - Add --ignore-errors negative,source --synthesize-missing flags to genhtml calls in run-tests-isolated.bash to match the multi-group runner and prevent HTML generation failures on coverage data with negative branch counts.	3 weeks ago
Rene Cannao	179644fed9	Fix ClickHouse test: use 0.0.0.0 interface for Docker compatibility The interface was set to 127.0.0.1 which is not accessible from another container. Changed to 0.0.0.0 which is replaced by the extract_module_host_port function with the correct hostname. Also update expected row count from 2 to 3 due to additional successful INSERT.	3 weeks ago
Rene Cannao	8ec472c771	Fix ClickHouse test: update expected row count after MergeTree fix After updating to new MergeTree syntax, the INSERT with NULL values now succeeds, resulting in 3 rows instead of 2.	3 weeks ago
Rene Cannao	3f91a44770	Fix ClickHouse tests: update MergeTree syntax and handle 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8ash - Added explicit `clickhouse-only` test group for isolated testing - Added quotes around hostname value in SET statements - Fixed 0.0.0 Docker.com doesn (including quotes around MergeTree syntax)	3 weeks ago
Rene Cannao	47907c2ead	Move test_client_limit_error-t to todo-g1 group This test uses network namespaces which don't work in Docker containers. Moving to todo-g1 for later review.	3 weeks ago
Rene Cannao	eac1adf7e1	Fix clickhouse tests for Docker-based CI infrastructure - Fix variable name: 'clickhouse-host' -> 'clickhouse-hostname' - Add quotes around hostname value in SET command - Handle 0.0.0.0 bind address: use 'proxysql' container hostname in Docker mode, or '127.0.0.1' for local execution	3 weeks ago
Rene Cannao	3acd6b31d6	Fix max_connections_ff-t: Use dynamic hostgroup discovery - Add discover_user_hostgroup() helper function to query default_hostgroup from mysql_users table instead of hardcoding hostgroup=0 - Update test_ff_sess_exceeds_max_conns() to use discovered hostgroup - Update test_ff_only_one_free_conn() to use discovered hostgroup - Update documentation to reflect dynamic hostgroup discovery - Add test/README.md with local CI execution instructions This allows the test to work with any infrastructure configuration (e.g., isolated CI where sbtest1 uses hostgroup 1300 instead of 0).	3 weeks ago
Rene Cannao	3ac0c2dd8a	Fix legacy TAP tests: clickhouse_php_conn and reg_test_3317 - clickhouse_php_conn-t.php: Fix deprecated ClickHouse MergeTree syntax Change from deprecated ENGINE=MergeTree(EventDate, (EventDate), 8192) to new syntax ENGINE=MergeTree() ORDER BY (EventDate) - reg_test_3317-lock_hostgroup_special_queries-t.cpp: Add query annotations Add /* ;hostgroup=1300 */ hints to SELECT statements to ensure proper routing when connection is locked to hostgroup 1300	3 weeks ago
Rene Cannao	7ee1332633	Add --ignore-errors source and --synthesize-missing to genhtml Fixes HTML generation errors for missing system headers like /usr/include/c++/13/bits/predefined_ops.h	3 weeks ago
Rene Cannao	20fc53e45c	Fix code coverage collection in multi-group test runner 1. Add set -e to run-multi-group.bash heredoc for proper error handling 2. Add EXIT trap in run-tests-isolated.bash to collect coverage on timeout/failure 3. Pass COVERAGE_MODE, COVERAGE_REPORT_DIR, and SCRIPT_DIR env vars to container 4. Fix fastcov invocation to use -e deps/ instead of restrictive -i filters 5. Add per-group HTML report generation 6. Run coverage combination in container for host without tools Coverage is now collected for: - include/ (189 header files) - lib/ (109 library files) - src/ (4 source files) The EXIT trap ensures coverage is collected even when tests timeout.	3 weeks ago
Rene Cannao	30620f37c4	Revert "Move coverage collection inside Docker container" This reverts commit `e571f08a45`.	3 weeks ago
Rene Cannao	e571f08a45	Move coverage collection inside Docker container Coverage collection now runs INSIDE the test-runner container immediately after tests complete (whether they succeed, fail, or timeout). This ensures: 1. Coverage data is collected even if the parent script times out 2. The .info file is generated inside the container before it exits 3. No dependency on external docker exec after container stops Also removes the external coverage collection code that was unreachable when timeout killed the subshell.	3 weeks ago
Rene Cannao	d9e9f2f059	Add coverage tools (lcov, fastcov) to proxysql-ci-base Docker image - Add lcov package for coverage report generation - Install fastcov via pip3 for faster coverage processing - Required for COVERAGE=1 mode in multi-group test runner	3 weeks ago
Rene Cannao	5f25df6c61	Improve test startup staggering with group-based hash	3 weeks ago
Rene Cannao	dcef810b99	Fix inner_exit_code unbound variable in run-multi-group.bash	3 weeks ago
Rene Cannao	9256a4c2f2	Fix heredoc variable expansion in run-multi-group.bash	3 weeks ago
Rene Cannao	5004d827b1	Fix proxysql-tester.py to fail when expected tests don't run	3 weeks ago
Rene Cannao	0d891b8941	Fix variable escaping in run-multi-group.bash subshell	3 weeks ago
Rene Cannao	64d8149a53	Add COVERAGE to run-multi-group.bash configuration summary output	3 weeks ago
Rene Cannao	9f6ba655bf	Add optional code coverage support for isolated test runs	3 weeks ago
Rene Cannao	40e5d785a6	Change multi-group startup delay from 0-15 to 1-20 seconds	3 weeks ago
Rene Cannao	cf54bff262	Fix docker-proxy-post.bash to use absolute path for .env sourcing The scripts were using relative path [ -f .env ] which failed when called from test/infra/control/, causing all SQL template variables (PREFIX, WHG, RHG, etc.) to be empty. This resulted in query rules with NULL match_digest patterns and incorrect rule IDs.	3 weeks ago
Rene Cannao	758b8116c8	Fix reg_test_3223 RESTAPI test by adding TAP group setup hook Fix reg_test_3223-restapi_return_codes-t failure: 1. Created test/tap/groups/legacy/setup-infras.bash: - TAP group hook that copies RESTAPI scripts to ProxySQL data directory - Sets execute permissions on all scripts EXCEPT script_no_permissions - Keeps script_no_permissions without execute permissions for EACCES test 2. Modified test/tap/groups/legacy/env.sh: - Added REGULAR_INFRA_DATADIR=/var/lib/proxysql - Points to where scripts are mounted inside ProxySQL container This follows the architectural principle that test-specific setup belongs in TAP group hooks, not in the generic test runner or infrastructure scripts.	4 weeks ago
Rene Cannao	33aae3b1c2	Fix reg_test_3223 RESTAPI scripts path and add group env inheritance Fix reg_test_3223-restapi_return_codes-t failure by properly configuring REGULAR_INFRA_DATADIR in group environment files: 1. test/tap/groups/legacy/env.sh: Add REGULAR_INFRA_DATADIR pointing to test/tap/tests where reg_test_3223_scripts directory exists 2. test/tap/groups/mysql84/env.sh: Same REGULAR_INFRA_DATADIR setting 3. Create env.sh for feature-specific groups: - mysql-auto_increment_delay_multiplex=0 - mysql-multiplexing=false - mysql-query_digests=0 - mysql-query_digests_keep_comment=1 4. test/scripts/bin/proxysql-tester.py: Add fallback logic to load base group env.sh when subgroup env.sh doesn't exist (e.g., legacy-g1 falls back to legacy). This follows the same pattern as ensure-infras.bash. This follows the architectural principle that test-specific setup belongs in TAP group configuration, not in the generic test runner.	4 weeks ago
Rene Cannao	ba7f45474e	Fix run-multi-group.bash bugs and improve robustness Fixes: - Fix array parsing issue with bash arithmetic expansion on group names Changed from 'read -ra GROUPS' to simple for-loop iteration Group names like 'legacy-g1' were being evaluated as arithmetic (1004-114-1=889) - Fix exit code capture from timeout command Changed from 'if ! timeout ...; then exit_code=$?' to proper '\|\| cmd_exit_code=$?' The old code was capturing the if-test exit code (0) instead of the command's - Change PARALLEL_JOBS default from 0 (unlimited) to 2 for resource safety Improvements: - Add random 0-15 second startup delay per group to stagger infrastructure initialization and prevent Docker/resource contention when running multiple groups in parallel - Update header documentation with new default values Tested with RUN_ID="abd123" TAP_GROUPS="legacy-g1 legacy-g2 ai-g1 mysql84-g1" which ran successfully with staggered startup.	4 weeks ago
Rene Cannao	472e3644f7	Add parallel TAP group execution scripts New scripts for running multiple TAP groups in parallel: - run-multi-group.bash: Orchestrates parallel execution of multiple TAP groups * RUN_ID: Links all groups in a single test run (e.g., commit SHA) * TAP_GROUPS: Space-separated list of groups to run * PARALLEL_JOBS: Limit concurrent groups (default: unlimited) * TIMEOUT_MINUTES: Per-group timeout (default: 60) * EXIT_ON_FIRST_FAIL: Stop on first failure (default: 0) * AUTO_CLEANUP: Destroy successful groups automatically (default: 0) * SKIP_CLUSTER_START: Skip ProxySQL cluster init (default: 0) - destroy-multi-group.bash: Bulk cleanup for a specific RUN_ID * Destroys all infrastructures matching -{RUN_ID} Can target specific groups or auto-discover from log directories Each group gets fully isolated infrastructure: - INFRA_ID: {TAP_GROUP}-{RUN_ID} - Network: {INFRA_ID}_backend - Per-group logs in ci_infra_logs/{INFRA_ID}/ Fixes #5463	4 weeks ago
Rene Cannao	679d758e24	Fix ai-g1 env.sh to be POSIX sh compatible The Python tester sources env files using /bin/sh, but the previous implementation used bash-specific features (BASH_SOURCE[0] and source). Changed to inline the values from ai/env.sh for POSIX compatibility.	4 weeks ago
Rene Cannao	2f8e63cef2	Address code review feedback for AI TAP group migration Fixes from PR #5461 review: 1. Fix BASE_GROUP derivation inconsistency in run-tests-isolated.bash - Changed from bash pattern matching `${TAP_GROUP%%-g[0-9]}` to sed - Now uses same pattern as ensure-infras.bash: `sed -E "s/[-_]g[0-9]+.//"` - Removed redundant BASE_GROUP reassignment 2. Update outdated comments in seed files - seed-mysql.sql and seed-pgsql.sql now correctly reference setup-infras.bash 3. Change INSERT OR IGNORE to INSERT OR REPLACE in mcp-config.sql - Ensures credentials are updated on reruns for deterministic state 4. Add shellcheck directives to env.sh files - Added `# shellcheck shell=bash` to ai/env.sh and ai-g1/env.sh 5. Add explicit validation for derived infrastructure names - setup-infras.bash now validates DEFAULT_MYSQL_INFRA and DEFAULT_PGSQL_INFRA - Provides clear error messages if infras.lst is misconfigured 6. Add WORKSPACE export to README examples - All runnable examples now include `export WORKSPACE=$(pwd)` Test verification: - ai-g1 group infrastructure setup works correctly - legacy-g2 group tests still pass (backward compatibility verified)	4 weeks ago
Rene Cannao	0b9806c46e	Migrate AI TAP group to Unified CI Infrastructure pattern This commit migrates the ai TAP group from its legacy hook-based approach to the standard test/infra/ Unified CI Infrastructure pattern. Changes: - Added generic hook system to infrastructure scripts: * ensure-infras.bash: Executes group-specific setup-infras.bash hook * run-tests-isolated.bash: Executes group-specific pre-cleanup.bash hook - Migrated ai group infrastructure: * Created infras.lst with infra-mysql84 and docker-pgsql16-single * Renamed seed files: mysql-seed.sql -> seed-mysql.sql, pgsql-seed.sql -> seed-pgsql.sql * Deleted legacy docker-compose.yml, docker-compose-init.bash, docker-compose-destroy.bash * Deleted legacy hooks: pre-proxysql.bash, post-proxysql.bash - Added group-specific MCP configuration: * setup-infras.bash: Configures MCP targets and seeds test data * pre-cleanup.bash: Removes MCP configuration after tests * mcp-config.sql: SQL template for MCP setup * cleanup.sql: SQL template for MCP cleanup * seed-mysql.sql & seed-pgsql.sql: Test data for AI tests - Updated documentation in README.md with usage examples Architecture: - ai is the supergroup (defines infrastructure and shared config) - ai-g1, ai-g2, etc. are subgroups (define test sets in groups.json) - Group-specific hooks live in test/tap/groups/ai/ directory - Infrastructure scripts remain generic and delegate to group hooks	4 weeks ago
René Cannaò	0c4e0cae6a	Merge pull request #8 from sysown/copilot/fix-tap-tests-legacy-g1 Fix legacy-g1 TAP tests broken by CI migration to per-container hostnames	4 weeks ago
René Cannaò	7e8ae3595e	Merge pull request #11 from sysown/agents/sysown1/9 fix(tests): Replace hardcoded 127.0.0.1 with env-driven host/port for CI isolation	4 weeks ago
sysown1	b354cb6639	fix(tests): Replace hardcoded 127.0.0.1 with env-driven host/port CI migration to Docker containers requires tests to use environment variables for host/port configuration instead of hardcoded localhost addresses. Changes: - test_cluster_sync-t.cpp: Use cl.host and cl.admin_port for DELETE queries - test_cluster_sync_mysql_servers-t.cpp: Use cl.host and cl.admin_port - test_read_only_actions_offline_hard_servers-t.cpp: Use cl.host and cl.admin_port - test_simple_embedded_HTTP_server-t.cpp: Use cl.host for HTTP requests The CommandLine class reads from TAP_ADMINHOST and TAP_ADMINPORT environment variables set by CI infrastructure, enabling tests to work in containerized environments where ProxySQL runs on a different hostname.	4 weeks ago
copilot-swe-agent[bot]	307fff98e0	Fix TAP tests failing in legacy/legacy-g1 after CI migration to per-container hostnames Co-authored-by: renecannao <3645227+renecannao@users.noreply.github.com>	4 weeks ago
copilot-swe-agent[bot]	bf4c511b1a	Initial plan	4 weeks ago
René Cannaò	680fac46c0	Merge pull request #6 from sysown/fix-clickhouse-php-test-1773942157 docs(infra): Add unique INFRA_ID and debug build instructions	4 weeks ago
sysown1	c2a45700ba	docs(infra): Add unique INFRA_ID and debug build instructions - Document that INFRA_ID must be unique using timestamps - Add ProxySQL debug build instructions for LOAD DEBUG FROM DISK support - Fix clickhouse-mysql_ifaces to listen on all interfaces (0.0.0.0) Related: #5	4 weeks ago
René Cannaò	458ef01970	Merge pull request #5453 from sysown/v3.0-ci_84 [WIP] multiple changes related to CI	4 weeks ago
Rene Cannao	e9b78ec572	Fix reg_test_3847_admin_lock for isolated CI runtime layout The legacy version of reg_test_3847_admin_lock assumed the old TAP execution model where everything effectively lived on 127.0.0.1 behind docker port mappings. In the new legacy-g2 infrastructure the test process and the primary ProxySQL run in separate containers, while the test still launches a second local ProxySQL instance inside the test container. That split exposed several test-side assumptions that were no longer valid and caused the child replica setup to fail before the actual deadlock coverage even started. The most important issue was how the secondary ProxySQL was started. The test passed a static proxysql_sec.cfg, but it did not give the child process an isolated datadir. On the new CI the child could therefore discover and reuse an existing proxysql.db from the default runtime location, which meant the tracked config file was not actually authoritative. The test would then wait for a replica on 127.0.0.1:26081 that never came up with the expected credentials or cluster topology. This change makes the secondary runtime explicit and self-contained. The test now creates a private runtime directory under test/tap/tests/reg_test_3847_node_datadir/runtime, generates the child config dynamically for the current environment, and launches the child with -D pointing at that runtime directory. The generated config keeps the local child replica on 127.0.0.1:26081/36081 while wiring the primary cluster peer to the real TAP admin endpoint discovered from CommandLine. That removes the stale single-host assumption and makes the test match how the isolated container environment is actually wired. The fix also cleans up endpoint usage inside the test body. Connections to the primary ProxySQL admin interface now use cl.admin_host/cl.admin_port instead of the generic frontend host, while the worker that talks to the locally spawned child explicitly targets 127.0.0.1:26081. This matters in the new CI because the primary lives in a different container but the child lives next to the test process. There was also a correctness bug in the thread bookkeeping. The previous code could overwrite a real worker error with success, and failed worker connections did not stop execution immediately. The worker status flags and launcher status are now atomic, connect failures return immediately, main-loop checks only treat positive errno values as failures, and shutdown waits report the live state instead of silently racing past it. Since this class of failure is expensive to diagnose remotely, the TAP diagnostics are intentionally much more verbose now. The test logs the primary and replica endpoints it is using, the generated config path, runtime directory, launcher capture log, internal ProxySQL log path, worker startup messages, periodic progress from the two background loops, wait-loop heartbeats, and shutdown progress. That should make future CI failures explain themselves from the TAP log instead of requiring ad hoc reproduction. Finally, add a local .gitignore entry for reg_test_3847_node_datadir/runtime/. That directory is generated by the test and contains transient databases, logs, and certificates for the spawned child ProxySQL instance; it should not be committed.	4 weeks ago
Rene Cannao	7384bea084	Fix reg_test_unexp_ping_pkt for isolated CI networking and Prometheus labels The reg_test_unexp_ping_pkt TAP failure on legacy-g2 was caused by multiple test-side issues that became visible after moving from host-local 127.0.0.1 execution with port mapping to isolated Docker containers on a private network. The first failure happened during the initial setup path: the test connected with ProxySQL root credentials and root host, but used cl.mysql_port instead of cl.root_port. In the old port-mapped layout this mistake could be masked more easily. In the isolated DNS-based setup used by legacy-g2, root/admin/frontend and backend ports are distinct and the mismatch causes an immediate connect failure. This change routes the setup connections through the correct ProxySQL root port and adds targeted connection diagnostics so future CI failures show the exact host, port, user, and MySQL error involved. The second failure was a latent prepared-statement bug in the test data loader. MYSQL_BIND.length pointed to a block-local variable that went out of scope before mysql_stmt_execute(), which led to intermittent or immediate client-side failures such as 'Client run out of memory' when inserting the large LONGTEXT payload used by the test. This change keeps the bound length alive for the full execution window and adds payload-size logging so the expensive setup phase is visible in TAP logs. The final failure was in metric validation, not in ProxySQL behavior. ProxySQL exports proxysql_mysql_unexpected_frontend_com_ping_total as a labeled Prometheus series, for example with {protocol="mysql"}. The test previously looked up the metric by exact key, which silently read zero from the parsed map and made the assertion fail even though ProxySQL was correctly detecting and handling the unexpected COM_PING packets. This change resolves the metric by prefix, records how many matching series were found, and logs the before/after values and delta explicitly. Verification: - rebuilt test/tap/tests/reg_test_unexp_ping_pkt-t - executed the test directly against the live legacy-g2 ProxySQL instance and observed ok 9 / exit 0 - executed the isolated CI-style path with TEST_PY_TAP_INCL=reg_test_unexp_ping_pkt-t via test/infra/control/run-tests-isolated.bash and observed PASS 1/294 : FAIL 0/294 This commit intentionally does not include unrelated orchestrator configuration edits that were already present in the worktree.	4 weeks ago
Rene Cannao	98c03d6fc6	Fix stale per-connection state tracking in set_testing-multi set_testing-multi batches 10 queries on the same MYSQL* connection, but it was still generating a fresh random connection index on every loop iteration. The test then used that random index for two different purposes that should have referred to the active batched connection instead:\n\n- logging conn_idx in the debug output\n- saving vars back into varsperconn\n\nThat meant 9 out of every 10 iterations could store one connection's accumulated expected session state into a different slot. When a later batch reused that slot, the test loaded stale or foreign expectations and reported a ProxySQL mismatch even though the backend and ProxySQL session state were correct.\n\nTrack the active connection index for the duration of each queries_per_connections batch and use it consistently when loading state, logging, and saving varsperconn. This makes the debug output trustworthy and prevents intermittent false failures such as the legacy-g2 set_testing-multi regression that appeared to implicate variable synchronization.	4 weeks ago
René Cannaò	07d43f627a	Merge pull request #5454 from sysown/v3.0-ci_84_mysql84 [WIP] CI changes	4 weeks ago

1 2 3 4 5 ...

8961 Commits (ca409366cb3fc0b5dbe85a8750c33ec88d4eebda) All Branches Search

8961 Commits (ca409366cb3fc0b5dbe85a8750c33ec88d4eebda)

All Branches