ci(integration-tests): Add GitHub workflow job to run CLP-core integration tests on every push.

.github/workflows/clp-artifact-build.yaml

@@ -103,6 +103,7 @@ jobs:
               - "components/core/src/**"
               - "components/core/tests/**"
               - "components/core/tools/scripts/utils/build-and-run-unit-tests.py"
+              - "integration-tests/**"
               - "taskfile.yaml"
               - "taskfiles/**"
               - "tools/scripts/deps-download/**"
@@ -575,7 +576,8 @@ jobs:
 
           mkdir -p "${output_dir}"
           cd "$GITHUB_WORKSPACE/components/core/build"
-          tar cfvv "${output_dir}/clp.tar" clg clp clp-s glt make-dictionaries-readable
+          tar cfvv "${output_dir}/clp.tar" \
+            clg clo clp clp-s glt indexer log-converter make-dictionaries-readable reducer-server
         shell: "bash"
 
       - if: "matrix.upload_binaries == true"
@@ -724,6 +726,57 @@ jobs:
               'build/lint-clang-tidy/**/*'
             )}}
 
+  ubuntu-jammy-integration-tests-core:
+    name: "ubuntu-jammy-integration-tests-core"
+    # Run if the ancestor jobs were successful/skipped and building clp was successful.
+    if: "!cancelled() && !failure() && needs.ubuntu-jammy-binaries.result == 'success'"
+    needs: "ubuntu-jammy-binaries"
+    runs-on: *runner
+    env:
+      OS_NAME: "ubuntu-jammy"
+      BUILD_DIR: "build"
+    steps:
+      - uses: "actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd"  # v6.0.2
+        with:
+          submodules: "recursive"
+          persist-credentials: false
+
+      - name: "Download the binaries artifact"
+        uses: "actions/download-artifact@95815c38cf2ff2164869cbab79da8d1f422bc89e"
+        with:
+          name: "${{env.BINARIES_ARTIFACT_NAME_PREFIX}}${{env.OS_NAME}}"
+          path: "${{env.BUILD_DIR}}/${{env.BINARIES_ARTIFACT_NAME_PREFIX}}${{env.OS_NAME}}"
+
+      - name: "Untar binaries"
+        working-directory: >-
+          ${{env.BUILD_DIR}}/${{env.BINARIES_ARTIFACT_NAME_PREFIX}}${{env.OS_NAME}}
+        run: |-
+          tar xf clp.tar
+          rm clp.tar
+
+      - name: "Install uv"
+        uses: "astral-sh/setup-uv@11f9893b081a58869d3b5fccaea48c9e9e46f990"  # v8.3.2
+
+      - name: "Install MariaDB Connector/C"
+        run: "sudo apt-get update && sudo apt-get install -y libmariadb-dev"
+
+      - name: "Run core integration tests"
+        working-directory: "integration-tests"
+        env:
+          CLP_BUILD_DIR: "../${{env.BUILD_DIR}}"
+          CLP_CORE_BINS_DIR: >-
+            ../${{env.BUILD_DIR}}/${{env.BINARIES_ARTIFACT_NAME_PREFIX}}${{env.OS_NAME}}
+          HOME: "/tmp"
+        run: "uv run pytest -m 'smoke or core'"
+
+      - name: "Upload the core integration test logs"
+        if: "always()"
+        uses: "actions/upload-artifact@b7c566a772e6b6bfb58ed0dc250532a479d7789f"  # v6.0.0
+        with:
+          name: "clp-integration-test-core-logs"
+          path: "${{env.BUILD_DIR}}/integration_tests/test_logs"
+          retention-days: 3
+
   package-image:
     name: "package-image-${{matrix.arch}}"
     # NOTE: The aarch64 job is skipped on PRs, so we accept both 'success' and 'skipped'.

docs/src/dev-docs/tooling-gh-workflows.md

@@ -8,7 +8,7 @@ builds, testing, and linting. We briefly describe each workflow below.
 This workflow is responsible for:
 
 1. building (Linux) container images containing CLP-core's dependencies,
-2. building CLP-core and running its unit tests, and
+2. building CLP-core and running its unit & integration tests, and 
 3. building a container image containing CLP's package components.
 
 To minimize build times, the jobs in the workflow are organized in the directed acyclic graph (DAG)
@@ -47,6 +47,7 @@ flowchart LR
     ubuntu-jammy-deps-image --> ubuntu-jammy-binaries
     ubuntu-jammy-deps-image --> package-image
     ubuntu-jammy-binaries --> ubuntu-jammy-binaries-image
+    ubuntu-jammy-binaries --> ubuntu-jammy-integration-tests-core
 :::
 
 Arrows between jobs indicate a dependency. The jobs are as follows:
@@ -80,6 +81,8 @@ Arrows between jobs indicate a dependency. The jobs are as follows:
   core's unit tests.
 * `ubuntu-jammy-binaries-image`: Builds an Ubuntu Jammy container image containing CLP-core's
   binaries built in the `ubuntu-jammy-binaries` job.
+* `ubuntu-jammy-integration-tests-core`: Runs CLP-core's integration tests using the binaries built
+  in the `ubuntu-jammy-binaries` job. The test logs are uploaded at the end of the test run.
 
 When the PR or commit doesn't change any of the files that affect CLP's dependencies (or the
 dependency container images), then the dependency container images won't be rebuilt; instead the

integration-tests/.pytest.ini

@@ -30,4 +30,5 @@ markers =
     core: mark tests that test the CLP core binaries
     package: mark tests that use the CLP package
     search: mark tests that test search
+    smoke: mark tests that are smoke tests
     startstop: mark tests that test start-stop

integration-tests/tests/test_clp_native_py_project_imports.py

@@ -1,11 +1,13 @@
 """Smoke tests to validate that CLP Python projects can be imported without errors."""
 
+import pytest
 from clp_mcp_server.constants import QueryJobType
 from clp_package_utils.general import JobType
 from clp_py_utils.clp_config import StorageEngine
 from job_orchestration.scheduler.constants import CompressionJobStatus
 
 
+@pytest.mark.smoke
 def test_clp_native_py_project_enum_classes() -> None:
     """
     Verifies that the following CLP Python projects can be imported successfully by testing