mariadb

mirror of https://github.com/MariaDB/server.git synced 2025-02-19 03:45:35 +01:00

History

Otto Kekalainen d1ba623677 All-green GitLab CI in main branch in January 2025 Ensure that the GitLab CI is green again. Ideally all failures would be fixed, but at the moment it is not feasible. As the purpose of a CI is to protect the code base from having new testable regressions slip in, update the CI pipeline to be all green by disabling multiple failing test or reduce their scope. - Avoid timeouts and make buid faster with '-DCPACK_RPM_DEBUGINFO_PACKAGE=OFF' - Remove 'GIT_CLONE_PATH' which isn't universally supported on all GitLab instances - Bump 'MARIADB_MAJOR_VERSION' to current 'main' contents (11.8). Also update the upgrade test matrix to modern MariaDB versions. - Remove UBsan builds as they are failing and can't quickly be fixed, along with the MTR test that depended on it. - Switch the CentOS 7 build to use Amazon Linux 2 instead, which has equivalent Fedora package versions, but is still maintained and package archive mirrors active. - Extend skiplist to include currently failing MTR tests. These are not quick to fix, so adding them to the skiplist will at least make the CI green and allow us to catch any new regressions. - Drop the default QPS limit in the mini-benchmark.sh to match what is currently passing. The drop is large because it wasn't adjusted after `4016c905` got merged. - Remove the currently failing faketime tests for 2028 compatibility. - Remove unnecessary `dependencies:` definitions that have no effect in the presence of `needs:` - Reduce the scope of `cppcheck` to avoid timeouts from job. - Update the ignorelists for both `cppcheck` and `flawfinder` as the jobs were failing. This way the jobs will be green again, and reveal is any new commits introduce issues. - Drop the duplicate `cppcheck` and `flawfinder` job definitions that got erroneously merged when both `9c287c0` and `f4ce1e4` got merged on the `main` branch, when the original intent was to have the latter commit only on old MariaDB versions. All new code of the whole pull request, including one or several files that are either new files or modified ones, are contributed under the BSD-new license. I am contributing on behalf of my employer Amazon Web Services, Inc.	2025-01-29 10:56:08 +11:00
..
cppcheck_ignorelist.txt	All-green GitLab CI in main branch in January 2025	2025-01-29 10:56:08 +11:00
flawfinder_ignorelist.json	All-green GitLab CI in main branch in January 2025	2025-01-29 10:56:08 +11:00

Otto Kekalainen d1ba623677 All-green GitLab CI in main branch in January 2025

Ensure that the GitLab CI is green again. Ideally all failures would be
fixed, but at the moment it is not feasible. As the purpose of a CI is
to protect the code base from having new testable regressions slip in,
update the CI pipeline to be all green by disabling multiple failing
test or reduce their scope.

- Avoid timeouts and make buid faster with
  '-DCPACK_RPM_DEBUGINFO_PACKAGE=OFF'

- Remove 'GIT_CLONE_PATH' which isn't universally supported on all
  GitLab instances

- Bump 'MARIADB_MAJOR_VERSION' to current 'main' contents (11.8). Also
  update the upgrade test matrix to modern MariaDB versions.

- Remove UBsan builds as they are failing and can't quickly be fixed,
  along with the MTR test that depended on it.

- Switch the CentOS 7 build to use Amazon Linux 2 instead, which has
  equivalent Fedora package versions, but is still maintained and
  package archive mirrors active.

- Extend skiplist to include currently failing MTR tests. These are not
  quick to fix, so adding them to the skiplist will at least make the
  CI green and allow us to catch any new regressions.

- Drop the default QPS limit in the mini-benchmark.sh to match what is
  currently passing. The drop is large because it wasn't adjusted after
  4016c905 got merged.

- Remove the currently failing faketime tests for 2028 compatibility.

- Remove unnecessary `dependencies:` definitions that have no effect in
  the presence of `needs:`

- Reduce the scope of `cppcheck` to avoid timeouts from job.

- Update the ignorelists for both `cppcheck` and `flawfinder` as the
  jobs were failing. This way the jobs will be green again, and reveal
  is any new commits introduce issues.

- Drop the duplicate `cppcheck` and `flawfinder` job definitions that
  got erroneously merged when both 9c287c0 and f4ce1e4 got merged on the
  `main` branch, when the original intent was to have the latter commit
  only on old MariaDB versions.

All new code of the whole pull request, including one or several files
that are either new files or modified ones, are contributed under the
BSD-new license. I am contributing on behalf of my employer
Amazon Web Services, Inc.

2025-01-29 10:56:08 +11:00

cppcheck_ignorelist.txt All-green GitLab CI in main branch in January 2025 2025-01-29 10:56:08 +11:00

flawfinder_ignorelist.json All-green GitLab CI in main branch in January 2025 2025-01-29 10:56:08 +11:00