Home - Waterfall Grid T-Grid Console Builders Recent Builds Buildslaves Changesources - JSON API - About

Console View


Categories: connectors experimental galera main
Legend:   Passed Failed Warnings Failed Again Running Exception Offline No data

connectors experimental galera main
f2b8d0f8b222...
f2b8d0f8b222d1b439243095f4bd5b1452c81ab8
Marko Mäkelä
Create and use backup.cnf; do not copy too much log
f21850007233...
f218500072335b0c8a9bbdc704646c73f7131279
Marko Mäkelä
fixup! f2b8d0f8b222d1b439243095f4bd5b1452c81ab8
e22c809911b1...
e22c809911b1148142baf1567e87fc7e4002d944
Marko Mäkelä
Revert "fixup! 5633fc2bf7fd070fd482f60063fd41c3298d36ac"

This reverts commit 5d04c41c3f353c7369fb1b2f16626b587120e31f.
e08a8fea1633...
e08a8fea1633b31b6a96582eef8d3b349741f1e5
Pekka Lampio
MDEV-38389: Galera test failure on galera_3nodes.galera_vote_majority_dml

Fix the broken Galera MTR test galera_3nodes.galera_vote_majority_dml
by restoring the value of the AUTO_INCREMENT_COUNTER at the end of the
test.
ddcdbf308c9e...
ddcdbf308c9ef605c0f7a490f174f5d42861b365
Dave Gosselin
MDEV-39602: Document the join_type enumeration

Replace the one line comment on join_type in sql_select.h with a
comment on each value.  Each comment explains what the access method
is, the conditions under which the optimizer chooses it, and what
EXPLAIN will show for it.
dae1a4907d43...
dae1a4907d43090a8040b9b9e90e5a6a3c1e01f0
Georg Richter
Backport CONC-805 to 3.3: Fix C23/glibc 2.43 const-correctness errors
  • cc-x-codbc-windows: 'dojob pwd if '3.4' == '3.4' ls win32/test SET TEST_DSN=master SET TEST_DRIVER=master SET TEST_PORT=3306 SET TEST_SCHEMA=odbcmaster if '3.4' == '3.4' cd win32/test if '3.4' == '3.4' ctest --output-on-failure' failed -  stdio
d93494e1e714...
d93494e1e7140d59a57443147d772c0acf4eb2d6
Marko Mäkelä
Chase ERROR_ACCESS_DENIED
d58b37999473...
d58b3799947382066d4a86516db54fa1a84a4408
Oleksandr Byelkin
Fix MDEV-39207 test (skip if ha_example is not built)
cf18a5b6ef83...
cf18a5b6ef8360c3ce764bec121a243097386ae6
bsrikanth-mariadb
MDEV-39791: Handle count aggregate optimization for replay purpose

During replay, when get_exact_record_count() is invoked from opt_sum_query(),
hook the recorded table rows from the parsed context for each table,
during the calculation of count.
c98c054dad4a...
c98c054dad4afc18b2b5a5d96ae40177d25fbda8
Sergei Petrunia
main.selectivity: add -disable_replay next_query Dont support optimizer_use_condition_selectivity=5
c92272458d1b...
c92272458d1b231f48ac89a9a07ed23374d41790
bsrikanth-mariadb
Fix opt_context_load_stats_basic test failures

New table stat fields got added, which cause the offset of the existing
test to change. Fixed the result file.
c7052b6dda45...
c7052b6dda45ae47146e7a3dc86c4e088d57bb2f
Sergei Petrunia
Save/restore handler->stats members: data_file_length, index_file_length, mean_rec_length.

This fixes mtr --replay-server innodb_ext_key.
c57010b93281...
c57010b93281c433cb7aa5fc7ed055df91c04c14
Sergei Petrunia
Add note_verbosity and sort_buffer size to relevant variables

note_verbosity fixes main.null_key test
sort_buffer_size fixes main.index_intersect_innodb
c44bc3b37775...
c44bc3b37775475cb609393bf9dc9c7f5e42db7c
Georg Richter
Merge branch '3.3-buildbot' into 3.3
  • cc-x-codbc-windows: 'dojob pwd if '3.4' == '3.4' ls win32/test SET TEST_DSN=master SET TEST_DRIVER=master SET TEST_PORT=3306 SET TEST_SCHEMA=odbcmaster if '3.4' == '3.4' cd win32/test if '3.4' == '3.4' ctest --output-on-failure' failed -  stdio
bec34dd2c90f...
bec34dd2c90f1ff328f8f862fe9a56a4879ac125
Georg Richter
Fix asan error:

Don't initialize mysql connection handle before
checking skip conditions
  • cc-x-codbc-windows: 'dojob pwd if '3.4' == '3.4' ls win32/test SET TEST_DSN=master SET TEST_DRIVER=master SET TEST_PORT=3306 SET TEST_SCHEMA=odbcmaster if '3.4' == '3.4' cd win32/test if '3.4' == '3.4' ctest --output-on-failure' failed -  stdio
bd17ca5d9e67...
bd17ca5d9e67a51f519ecefe87113dc6616058de
bsrikanth-mariadb
--disable_replay: show_explain, update

disable tests that have subqueries computed at optimization time
badcc1764a5b...
badcc1764a5b2a79455396ae970cdaa28fc53fa5
Razvan Liviu Varzaru
MDBF-1214 Use HEAD for Git source package archives (#312)

MDBF-1214 Clean up and simplify Git source archive generation

Buildbot source package builds can run from a shallow detached checkout
created by fetching a specific commit and checking out FETCH_HEAD. In that
state, git show-branch may not report a branch name, leaving GIT_BRANCH
empty and causing git archive to fail.

To resolve this, archive HEAD directly instead. This packages the commit
that CMake is building, regardless of whether it was checked out from
a branch, tag, or detached CI commit.

Additionally, this simplifies the archive generation logic:
- Combined the duplicated zip archive commands for WIN32 and non-WIN32
  branches into a single command before the platform-specific block.
- On non-Windows platforms, configured git archive to write tar.gz directly,
  eliminating the separate, uncompressed tar and gzip compression step.
  • cc-x-codbc-windows: 'dojob pwd if '3.4' == '3.4' ls win32/test SET TEST_DSN=master SET TEST_DRIVER=master SET TEST_PORT=3306 SET TEST_SCHEMA=odbcmaster if '3.4' == '3.4' cd win32/test if '3.4' == '3.4' ctest --output-on-failure' failed -  stdio
abe57f0b5158...
abe57f0b5158d5838d4b522f47c942cc4644c0f4
Pekka Lampio
MDEV-38389: Galera test failure on galera_3nodes.galera_vote_majority_dml

Fix the broken Galera MTR test galera_3nodes.galera_vote_majority_dml
by restoring the value of the AUTO_INCREMENT_OFFSET at the end of the
test.
a37492c46f81...
a37492c46f8107986c2f486c1b03dface9299d34
Michal Schorm
CONC-813, CONC-814 Fix UBSan errors

sint4korr (non-x86 path): the expression
`(int16)(A)[3] << 24` causes signed integer overflow
when byte value >= 128, since 128<<24 exceeds INT32_MAX.
Redefine as `(int32) uint4korr(A)` to compute in unsigned
arithmetic, matching the server (my_byteorder.h:137-140).
The next line sint8korr already uses this same pattern:
`(longlong) uint8korr(A)`.

convert_from_long (MYSQL_TYPE_DOUBLE, MYSQL_TYPE_FLOAT):
casting double/float back to ulonglong/longlong for
truncation detection is undefined when the float value
is outside the representable integer range. For example,
`(double)ULONGLONG_MAX` rounds up to 2^64 in IEEE 754
(not exactly representable with 53-bit mantissa), so
`(ulonglong)dbl` overflows. Similarly for LONGLONG_MAX.
Add range checks before the cast using `>=` for upper
bounds (since the double rounds up past the integer max)
and `<` for LONGLONG_MIN (exactly representable as -2^63).
Out-of-range values set the truncation error flag directly,
short-circuiting the dangerous cast via `||` evaluation.
This matches the server pattern in sql/field.cc and
sql/sql_select.cc (double_to_ulonglong macro).

Co-Authored-By: Claude AI <[email protected]>
  • cc-x-codbc-windows: 'dojob pwd if '3.4' == '3.4' ls win32/test SET TEST_DSN=master SET TEST_DRIVER=master SET TEST_PORT=3306 SET TEST_SCHEMA=odbcmaster if '3.4' == '3.4' cd win32/test if '3.4' == '3.4' ctest --output-on-failure' failed -  stdio
96f69a7fec41...
96f69a7fec41d3b638cdb49036059071cfc82ed2
Sergei Golubchik
MDEV-30041 don't set utf8_is_utf8mb3 by default in the old-mode
958404cfeb96...
958404cfeb96723c807704bbd653fa617d68feda
Marko Mäkelä
Chase ERROR_ACCESS_DENIED
8e1fbc6bad1a...
8e1fbc6bad1a4bd1e745f37f881a89da7072bdd1
Alexey Botchkov
MDEV-37262 XMLISVALID() schema validation function.

XMLVALID function added to the XMLTYPE plugin.
8d9342ea0c66...
8d9342ea0c6604e81cbb99c816dd4d56362120fd
bsrikanth-mariadb
MDEV-39538: Different costs when same range is read twice

When same range is used as a filter, once in the outer query block, and
the second inside a sub query such as: -

select * from t1
  where year(a) = 2010 and c < (select count(*) from t1 where year(a) = 2010);

The Optimizer Context had two records for multi_range_read_info_const() call,
but had different cost vector members.
The cause is that the first table considered index-only scan on the range,
while the second considered non-index only scan.

However, when replaying the context, the same range got matched
twice, and the costs corresponding to that got returned twice.
Hence the costs in the explain plan output differed as well.

Solution
========
Include a new field called "call_number", while recording range contexts
into the overall context. This way, we could even match the call_number
and return the appropriate cost during replay.
8be108b89eba...
8be108b89eba36a7afb218a8dd1c84d909bbd181
bsrikanth-mariadb
MDEV-39538: Different costs when same range is read twice

When same range is used as a filter, once in the outer query block, and
the second inside a sub query such as: -

select * from t1
  where year(a) = 2010 and c < (select count(*) from t1 where year(a) = 2010);

The Optimizer Context had two records for multi_range_read_info_const() call,
but had different cost vector members.
The cause is that the first table considered index-only scan on the range,
while the second considered non-index only scan.

However, when replaying the context, the same range got matched
twice, and the costs corresponding to that got returned twice.
Hence the costs in the explain plan output differed as well.

Solution
========
Include a new field called "call_number", while recording range contexts
into the overall context. This way, we could even match the call_number
and return the appropriate cost during replay.
8b483385c379...
8b483385c379f36139c4ac6e8786e5f6a791f32c
Sergei Petrunia
Fix replay with main.subselect_mat_cost test

In the context, "rec_per_key" stores doubles, quoted.
Do not attempt to read them as strings.
798584db962f...
798584db962fd9d80f5b9c36f5a0ba2d9b0a7120
Razvan Liviu Varzaru
MDBF-1214 Add WITH_{MSAN, ASAN, UBSAN} CMake support (#313)

* MDBF-1214 Add WITH_MSAN CMake support

Declare WITH_MSAN as a regular option for standalone Connector/C
builds.

When enabled directly in Connector/C, append MemorySanitizer compile and
link flags for Debug and RelWithDebInfo builds.

When Connector/C is included as a subproject, keep using the inherited
WITH_MSAN value only for sanitizer-specific linker behavior. This avoids
duplicating sanitizer flags already managed by parent projects.

* MDBF-1214 Add ASAN and UBSAN CMake support

Add standalone Connector/C options for WITH_ASAN and WITH_UBSAN.

Use a shared sanitizer flag helper for Debug and RelWithDebInfo builds,
covering compile flags and executable/shared/module linker flags.

Keep the flag handling disabled for subproject builds so Connector/C++
and ODBC continue to own sanitizer flags for their combined builds.

* MDBF-1214 Refine sanitizer CMake options

Add an opt-in WITH_ASAN_SCOPE option for Clang builds so ASAN can detect stack use after scope without adding the flag to linker options.

Enable MSVC ASAN stack use after return instrumentation and keep incremental linking disabled for those builds.

Reject MSAN when ASAN or UBSAN is also enabled. Remove the redundant ASAN -fPIC flag and keep UBSAN alignment checks enabled.
  • cc-x-codbc-windows: 'dojob pwd if '3.4' == '3.4' ls win32/test SET TEST_DSN=master SET TEST_DRIVER=master SET TEST_PORT=3306 SET TEST_SCHEMA=odbcmaster if '3.4' == '3.4' cd win32/test if '3.4' == '3.4' ctest --output-on-failure' failed -  stdio
75640266ecb4...
75640266ecb456168c5b3945e6c733bb693cc9f2
Georg Richter
bump the version to 3.3.20
  • cc-x-codbc-windows: 'dojob pwd if '3.4' == '3.4' ls win32/test SET TEST_DSN=master SET TEST_DRIVER=master SET TEST_PORT=3306 SET TEST_SCHEMA=odbcmaster if '3.4' == '3.4' cd win32/test if '3.4' == '3.4' ctest --output-on-failure' failed -  stdio
6239e06cb58a...
6239e06cb58af1107fba5dc3b7f4056819ab35b5
Sergei Golubchik
CONC-820 alloca() on invalid metadata from the server

in a valid packet field->length for zero-filled longs cannot exceed 255
620f51422181...
620f514221815d1de9d586d592b159478d9241d4
Sergei Petrunia
More --disable_replay: join_cache, subselect_mat_cost
5c9ac44c1413...
5c9ac44c1413d92aed1ea9e49a26a929c4e7f52f
bsrikanth-mariadb
MDEV-39791: Handle count aggregate optimization for replay purpose

During replay, when get_exact_record_count() is invoked from opt_sum_query(),
hook the recorded table rows from the parsed context for each table,
during the calculation of count.
5b32c182fc11...
5b32c182fc110417b55f06fd3ae01516fc458336
Sergei Petrunia
Add --disable_replay in main.key
3efa973f41af...
3efa973f41affb1b81489268e16e5118dd2bce70
bsrikanth-mariadb
MDEV-39538: Different costs when same range is read twice

When same range is used as a filter, once in the outer query block, and
the second inside a sub query such as: -

select * from t1
  where year(a) = 2010 and c < (select count(*) from t1 where year(a) = 2010);

The Optimizer Context had two records for multi_range_read_info_const() call,
but had different cost vector members.
The cause is that the first table considered index-only scan on the range,
while the second considered non-index only scan.

However, when replaying the context, the same range got matched
twice, and the costs corresponding to that got returned twice.
Hence the costs in the explain plan output differed as well.

Solution
========
Include a new field called "call_number", while recording range contexts
into the overall context. This way, we could even match the call_number
and return the appropriate cost during replay.
3ca859c6200d...
3ca859c6200df96ff3268b8ed722cf0489cf073f
Georg Richter
Merge pull request #301 from heitbaum/patch-1

[CONC-805] fix assignment discards 'const' qualifier
  • cc-x-codbc-windows: 'dojob pwd if '3.4' == '3.4' ls win32/test SET TEST_DSN=master SET TEST_DRIVER=master SET TEST_PORT=3306 SET TEST_SCHEMA=odbcmaster if '3.4' == '3.4' cd win32/test if '3.4' == '3.4' ctest --output-on-failure' failed -  stdio
3947c056346f...
3947c056346f19215af6b58deb90882ec94e83a6
Marko Mäkelä
Create and use backup.cnf; do not copy too much log
302bd8f230da...
302bd8f230da2ca79762a634cc171251f9e6f052
bsrikanth-mariadb
MDEV-39538: Different costs when same range is read twice

When same range is used as a filter, once in the outer query block, and
the second inside a sub query such as: -

select * from t1
  where year(a) = 2010 and c < (select count(*) from t1 where year(a) = 2010);

The Optimizer Context had two records for multi_range_read_info_const() call,
but had different cost vector members.
The cause is that the first table considered index-only scan on the range,
while the second considered non-index only scan.

However, when replaying the context, the same range got matched
twice, and the costs corresponding to that got returned twice.
Hence the costs in the explain plan output differed as well.

Solution
========
Include a new field called "call_number", while recording range contexts
into the overall context. This way, we could even match the call_number
and return the appropriate cost during replay.
1f56d9c3feee...
1f56d9c3feeeca82661cbe57cb628207c8b186f8
Oleksandr Byelkin
Fix MDEV-39207 test (skip if ha_example is not built)
1269e3fcb6f3...
1269e3fcb6f3fed1963da52f173d2491d5df3c65
Georg Richter
Merge branch '3.3' into 3.4
  • cc-x-codbc-windows: 'dojob pwd if '3.4' == '3.4' ls win32/test SET TEST_DSN=master SET TEST_DRIVER=master SET TEST_PORT=3306 SET TEST_SCHEMA=odbcmaster if '3.4' == '3.4' cd win32/test if '3.4' == '3.4' ctest --output-on-failure' failed -  stdio
BuildBot (0.8.9) working for the MariaDB project.
Page built: Thu 04 Jun 2026 20:02:57 (UTC)