build: split integration test and run in parallel by driessamyn · Pull Request #111 · driessamyn/kapper

driessamyn · 2025-04-25T16:22:53Z

No description provided.

qodo-free-for-open-source-projects · 2025-04-25T16:23:09Z

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
General	✅ ~~Add job dependency~~ Suggestion Impact: The commit implemented the suggestion by adding a 'needs' parameter to the integration-test job that depends on the 'build' job, ensuring proper workflow sequencing code diff: + needs: + - build The new integration test job is missing a dependency on the main build job. Add a 'needs' parameter to ensure integration tests run after the main build completes. .github/workflows/build-and-test.yml [75-78] integration-test: name: Integration tests runs-on: ubuntu-latest + needs: build steps: `[Suggestion has been applied]` Suggestion importance[1-10]: 9 __ Why: The suggestion correctly points out that the new integration test job lacks a dependency on the main build job. Adding 'needs: build' ensures proper workflow sequencing, preventing potential race conditions and ensuring integration tests run only after a successful build.	High
Possible issue	✅ ~~Maintain full code analysis~~ Suggestion Impact: The commit changed the Gradle command from 'test sonar' to 'check sonar', which is similar to the suggested 'build sonar' command. Both 'check' and 'build' ensure more comprehensive code analysis than just 'test'. code diff: - run: ./gradlew test sonar + run: ./gradlew check sonar The PR changes the Gradle command from 'build sonar -Ddb=all' to 'test sonar', which might cause Sonar to analyze only test code instead of the full build. Ensure Sonar still analyzes all relevant code. .github/workflows/build-and-test.yml [40-43] - name: Build & Test with Gradle env: SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }} - run: ./gradlew test sonar + run: ./gradlew build sonar `[Suggestion has been applied]` Suggestion importance[1-10]: 8 __ Why: The suggestion correctly identifies that changing from 'build sonar -Ddb=all' to 'test sonar' might limit Sonar's analysis to only test code instead of the full codebase. This could significantly impact code quality monitoring.	Medium
Update

Copilot

Pull Request Overview

This PR splits integration tests from the main build process to allow parallel execution and improve build efficiency. Key changes include:

Adding caching for Gradle in the build workflow.
Modifying the Gradle command in the main build job to run only unit tests with sonar analysis.
Introducing a new integration-test job that executes integration tests separately.

Comments suppressed due to low confidence (2)

.github/workflows/build-and-test.yml:75

Ensure that the separation between unit tests and integration tests is fully reflected in your Gradle configuration to avoid duplicate test execution or gaps in test coverage.

integration-test:

.github/workflows/build-and-test.yml:43

The removal of '-Ddb=all' from the unit test command may lead to unintended test configuration differences if the flag was previously used to set up the test database environment. Verify that this change is intentional and that the new integration-test job correctly manages the required environment configuration.

run: ./gradlew test sonar

qodo-free-for-open-source-projects · 2025-04-25T16:25:39Z

CI Feedback 🧐

(Feedback updated until commit `bef6dec`)

A test triggered by this PR failed. Here is an AI-generated analysis of the failure:

Action: Analyze (Kotlin)
Failed stage: Perform CodeQL Analysis [❌]
Failure summary: The CodeQL analysis failed because it could not process any Java/Kotlin code in the repository. The specific error message at line 1148 states: "CodeQL detected code written in Java/Kotlin but could not process any of it." This typically happens when: 1. The build process didn't properly compile the Java/Kotlin code 2. The CodeQL analyzer couldn't trace the build process correctly 3. Source files were detected but not processed during the build The action exited with code 32, indicating a fatal error during the database finalization step.
Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 443: { 444: "extractor_root" : "/opt/hostedtoolcache/CodeQL/2.21.1/x64/codeql/html" 445: } 446: ], 447: "python" : [ 448: { 449: "extractor_root" : "/opt/hostedtoolcache/CodeQL/2.21.1/x64/codeql/python", 450: "extractor_options" : { 451: "logging" : { 452: "title" : "Options pertaining to logging.", 453: "description" : "Options pertaining to logging.", 454: "type" : "object", 455: "properties" : { 456: "verbosity" : { 457: "title" : "Python extractor logging verbosity level.", 458: "description" : "Controls the level of verbosity of the CodeQL Python extractor.\nThe supported levels are (in order of increasing verbosity):\n\n - off\n - errors\n - warnings\n - info or progress\n - debug or progress+\n - trace or progress++\n - progress+++\n", 459: "type" : "string", 460: "pattern" : "^(off\|errors\|warnings\|(info\|progress)\|(debug\|progress\\+)\|(trace\|progress\\+\\+)\|progress\\+\\+\\+)$" 461: } ... 493: } 494: }, 495: "buildless" : { 496: "title" : "DEPRECATED - Whether to use buildless (standalone) extraction.", 497: "description" : "DEPRECATED: Use `--build-mode none` instead.\nA value indicating, which type of extraction the autobuilder should perform. If 'true', then the standalone extractor will be used, otherwise tracing extraction will be performed. The default is 'false'. Note that buildless extraction will generally yield less accurate analysis results, and should only be used in cases where it is not possible to build the code (for example if it uses inaccessible dependencies).\n", 498: "type" : "string", 499: "pattern" : "^(false\|true)$" 500: }, 501: "logging" : { 502: "title" : "Options pertaining to logging.", 503: "description" : "Options pertaining to logging.", 504: "type" : "object", 505: "properties" : { 506: "verbosity" : { 507: "title" : "Extractor logging verbosity level.", 508: "description" : "Controls the level of verbosity of the extractor. The supported levels are (in order of increasing verbosity):\n - off\n - errors\n - warnings\n - info or progress\n - debug or progress+\n - trace or progress++\n - progress+++\n", 509: "type" : "string", 510: "pattern" : "^(off\|errors\|warnings\|(info\|progress)\|(debug\|progress\\+)\|(trace\|progress\\+\\+)\|progress\\+\\+\\+)$" 511: } ... 769: { 770: "extractor_root" : "/opt/hostedtoolcache/CodeQL/2.21.1/x64/codeql/html" 771: } 772: ], 773: "python" : [ 774: { 775: "extractor_root" : "/opt/hostedtoolcache/CodeQL/2.21.1/x64/codeql/python", 776: "extractor_options" : { 777: "logging" : { 778: "title" : "Options pertaining to logging.", 779: "description" : "Options pertaining to logging.", 780: "type" : "object", 781: "properties" : { 782: "verbosity" : { 783: "title" : "Python extractor logging verbosity level.", 784: "description" : "Controls the level of verbosity of the CodeQL Python extractor.\nThe supported levels are (in order of increasing verbosity):\n\n - off\n - errors\n - warnings\n - info or progress\n - debug or progress+\n - trace or progress++\n - progress+++\n", 785: "type" : "string", 786: "pattern" : "^(off\|errors\|warnings\|(info\|progress)\|(debug\|progress\\+)\|(trace\|progress\\+\\+)\|progress\\+\\+\\+)$" 787: } ... 819: } 820: }, 821: "buildless" : { 822: "title" : "DEPRECATED - Whether to use buildless (standalone) extraction.", 823: "description" : "DEPRECATED: Use `--build-mode none` instead.\nA value indicating, which type of extraction the autobuilder should perform. If 'true', then the standalone extractor will be used, otherwise tracing extraction will be performed. The default is 'false'. Note that buildless extraction will generally yield less accurate analysis results, and should only be used in cases where it is not possible to build the code (for example if it uses inaccessible dependencies).\n", 824: "type" : "string", 825: "pattern" : "^(false\|true)$" 826: }, 827: "logging" : { 828: "title" : "Options pertaining to logging.", 829: "description" : "Options pertaining to logging.", 830: "type" : "object", 831: "properties" : { 832: "verbosity" : { 833: "title" : "Extractor logging verbosity level.", 834: "description" : "Controls the level of verbosity of the extractor. The supported levels are (in order of increasing verbosity):\n - off\n - errors\n - warnings\n - info or progress\n - debug or progress+\n - trace or progress++\n - progress+++\n", 835: "type" : "string", 836: "pattern" : "^(off\|errors\|warnings\|(info\|progress)\|(debug\|progress\\+)\|(trace\|progress\\+\\+)\|progress\\+\\+\\+)$" 837: } ... 976: CODEQL_EXTRACTOR_JAVA_TRAP_DIR: /home/runner/work/_temp/codeql_databases/java/trap/java 977: CODEQL_EXTRACTOR_JAVA_SOURCE_ARCHIVE_DIR: /home/runner/work/_temp/codeql_databases/java/src 978: CODEQL_EXTRACTOR_JAVA_THREADS: 4 979: CODEQL_EXTRACTOR_JAVA_RAM: 14575 980: CODEQL_TRACER_LOG: /home/runner/work/_temp/codeql_databases/log/build-tracer.log 981: CODEQL_TRACER_DIAGNOSTICS_DIR: /home/runner/work/_temp/codeql_databases/diagnostic/tracer 982: CODEQL_TRACER_LANGUAGES: java 983: SEMMLE_PRELOAD_libtrace: /opt/hostedtoolcache/CodeQL/2.21.1/x64/codeql/tools/linux64/${LIB}_${PLATFORM}_trace.so 984: SEMMLE_PRELOAD_libtrace32: /opt/hostedtoolcache/CodeQL/2.21.1/x64/codeql/tools/linux64/lib32trace.so 985: SEMMLE_PRELOAD_libtrace64: /opt/hostedtoolcache/CodeQL/2.21.1/x64/codeql/tools/linux64/lib64trace.so 986: CODEQL_RUNNER: /opt/hostedtoolcache/CodeQL/2.21.1/x64/codeql/tools/linux64/runner 987: LD_PRELOAD: /opt/hostedtoolcache/CodeQL/2.21.1/x64/codeql/tools/linux64/${LIB}_${PLATFORM}_trace.so 988: ##[endgroup] 989: Welcome to Gradle 8.12! 990: Here are the highlights of this release: 991: - Enhanced error and warning reporting with the Problems API 992: - File-system watching support on Alpine Linux 993: - Build and test Swift 6 libraries and apps 994: For more details see https://docs.gradle.org/8.12/release-notes.html 995: Starting a Gradle Daemon (subsequent builds will be faster) 996: > Task :buildSrc:checkKotlinGradlePluginConfigurationErrors SKIPPED 997: > Task :buildSrc:generateExternalPluginSpecBuilders FROM-CACHE 998: > Task :buildSrc:extractPrecompiledScriptPluginPlugins FROM-CACHE 999: > Task :buildSrc:compilePluginsBlocks FROM-CACHE 1000: > Task :buildSrc:generatePrecompiledScriptPluginAccessors FROM-CACHE 1001: > Task :buildSrc:generateScriptPluginAdapters FROM-CACHE 1002: > Task :buildSrc:compileKotlin FROM-CACHE 1003: > Task :buildSrc:compileJava NO-SOURCE 1004: > Task :buildSrc:compileGroovy NO-SOURCE 1005: > Task :buildSrc:pluginDescriptors 1006: > Task :buildSrc:processResources 1007: > Task :buildSrc:classes 1008: > Task :buildSrc:jar 1009: > Task :clean UP-TO-DATE 1010: > Task :kapper:clean UP-TO-DATE 1011: > Task :kapper-benchmark:clean UP-TO-DATE 1012: > Task :kapper-coroutines:clean UP-TO-DATE 1013: > Task :checkKotlinGradlePluginConfigurationErrors SKIPPED 1014: > Task :compileKotlin NO-SOURCE 1015: > Task :compileJava NO-SOURCE 1016: > Task :processResources NO-SOURCE 1017: > Task :classes UP-TO-DATE 1018: > Task :jar 1019: > Task :assemble 1020: > Task :kapper:checkKotlinGradlePluginConfigurationErrors SKIPPED 1021: > Task :kapper:loadKtlintReporters FROM-CACHE ... 1025: > Task :kapper:ktlintKotlinScriptFormat FROM-CACHE 1026: > Task :kapper:runKtlintFormatOverMainSourceSet FROM-CACHE 1027: > Task :kapper:ktlintMainSourceSetFormat FROM-CACHE 1028: > Task :kapper:runKtlintFormatOverTestSourceSet FROM-CACHE 1029: > Task :kapper:ktlintTestSourceSetFormat FROM-CACHE 1030: > Task :kapper:ktlintFormat UP-TO-DATE 1031: > Task :kapper:compileKotlin FROM-CACHE 1032: > Task :kapper:compileJava NO-SOURCE 1033: > Task :kapper:processResources NO-SOURCE 1034: > Task :kapper:classes UP-TO-DATE 1035: > Task :kapper:jar 1036: > Task :kapper:javadoc NO-SOURCE 1037: > Task :kapper:javadocJar 1038: > Task :kapper:sourcesJar 1039: > Task :kapper:assemble 1040: > Task :kapper-benchmark:checkKotlinGradlePluginConfigurationErrors SKIPPED 1041: > Task :kapper-benchmark:loadKtlintReporters FROM-CACHE 1042: > Task :kapper-benchmark:runKtlintFormatOverKotlinScripts NO-SOURCE 1043: > Task :kapper-benchmark:runKtlintFormatOverIntegrationTestSourceSet FROM-CACHE 1044: > Task :kapper-benchmark:ktlintIntegrationTestSourceSetFormat FROM-CACHE 1045: > Task :kapper-benchmark:runKtlintFormatOverJmhSourceSet FROM-CACHE 1046: > Task :kapper-benchmark:ktlintJmhSourceSetFormat FROM-CACHE 1047: > Task :kapper-benchmark:ktlintKotlinScriptFormat SKIPPED 1048: > Task :kapper-benchmark:runKtlintFormatOverMainSourceSet FROM-CACHE 1049: > Task :kapper-benchmark:ktlintMainSourceSetFormat FROM-CACHE 1050: > Task :kapper-benchmark:runKtlintFormatOverTestSourceSet NO-SOURCE 1051: > Task :kapper-benchmark:ktlintTestSourceSetFormat SKIPPED 1052: > Task :kapper-benchmark:ktlintFormat UP-TO-DATE 1053: > Task :kapper-coroutines:checkKotlinGradlePluginConfigurationErrors SKIPPED 1054: > Task :kapper-coroutines:loadKtlintReporters FROM-CACHE ... 1085: Publishing build scan... 1086: gradle/actions: Writing build results to /home/runner/work/_temp/.gradle-actions/build-scans/__run-1745781608527.json 1087: https://gradle.com/s/ol3pf6ucvucky 1088: ##[group]Run github/codeql-action/analyze@v3 1089: with: 1090: output: ../results 1091: upload: always 1092: cleanup-level: brutal 1093: add-snippets: false 1094: skip-queries: false 1095: checkout_path: /home/runner/work/kapper/kapper 1096: upload-database: true 1097: wait-for-processing: true 1098: token: *** 1099: matrix: null 1100: expect-error: false 1101: env: ... 1134: CODEQL_EXTRACTOR_JAVA_THREADS: 4 1135: CODEQL_EXTRACTOR_JAVA_RAM: 14575 1136: CODEQL_TRACER_LOG: /home/runner/work/_temp/codeql_databases/log/build-tracer.log 1137: CODEQL_TRACER_DIAGNOSTICS_DIR: /home/runner/work/_temp/codeql_databases/diagnostic/tracer 1138: CODEQL_TRACER_LANGUAGES: java 1139: SEMMLE_PRELOAD_libtrace: /opt/hostedtoolcache/CodeQL/2.21.1/x64/codeql/tools/linux64/${LIB}_${PLATFORM}_trace.so 1140: SEMMLE_PRELOAD_libtrace32: /opt/hostedtoolcache/CodeQL/2.21.1/x64/codeql/tools/linux64/lib32trace.so 1141: SEMMLE_PRELOAD_libtrace64: /opt/hostedtoolcache/CodeQL/2.21.1/x64/codeql/tools/linux64/lib64trace.so 1142: CODEQL_RUNNER: /opt/hostedtoolcache/CodeQL/2.21.1/x64/codeql/tools/linux64/runner 1143: LD_PRELOAD: /opt/hostedtoolcache/CodeQL/2.21.1/x64/codeql/tools/linux64/${LIB}_${PLATFORM}_trace.so 1144: ##[endgroup] 1145: While resolving threads, found a cgroup CPUs file with 4 CPUs in /sys/fs/cgroup/cpuset.cpus.effective. 1146: ##[group]Finalizing java 1147: [command]/opt/hostedtoolcache/CodeQL/2.21.1/x64/codeql/codeql database finalize --finalize-dataset --threads=4 --ram=14575 /home/runner/work/_temp/codeql_databases/java 1148: CodeQL detected code written in Java/Kotlin but could not process any of it. For more information, review our troubleshooting guide at https://gh.io/troubleshooting-code-scanning/no-source-code-seen-during-build . 1149: ##[error]Encountered a fatal error while running "/opt/hostedtoolcache/CodeQL/2.21.1/x64/codeql/codeql database finalize --finalize-dataset --threads=4 --ram=14575 /home/runner/work/_temp/codeql_databases/java". Exit code was 32 and last log line was: CodeQL detected code written in Java/Kotlin but could not process any of it. For more information, review our troubleshooting guide at https://gh.io/troubleshooting-code-scanning/no-source-code-seen-during-build . See the logs for more details. 1150: Post job cleanup. 1151: Post job cleanup. 1152: [command]/opt/hostedtoolcache/CodeQL/2.21.1/x64/codeql/codeql database export-diagnostics /home/runner/work/_temp/codeql_databases --db-cluster --format=sarif-latest --output=../codeql-failed-run.sarif --sarif-include-diagnostics -vvv 1153: Writing logs to /home/runner/work/_temp/codeql_databases/log/database-export-diagnostics-20250427.192030.205.log. 1154: Interpreting diagnostic messages... 1155: Looking for diagnostics in /home/runner/work/_temp/codeql_databases/java/diagnostic... 1156: Found diagnostics file /home/runner/work/_temp/codeql_databases/java/diagnostic/cli-diagnostics-add-20250427T192027.125Z.json. 1157: Looking for diagnostics in /home/runner/work/_temp/codeql_databases/java/diagnostic/codeql-action... 1158: Found diagnostics file /home/runner/work/_temp/codeql_databases/java/diagnostic/codeql-action/codeql-action-2025-04-27T191951.934Z.json. 1159: Looking for diagnostics in /home/runner/work/_temp/codeql_databases/java/diagnostic/extractors... 1160: Looking for diagnostics in /home/runner/work/_temp/codeql_databases/java/diagnostic/extractors/java... 1161: Looking for diagnostics in /home/runner/work/_temp/codeql_databases/diagnostic... 1162: Looking for diagnostics in /home/runner/work/_temp/codeql_databases/diagnostic/tracer... 1163: Found 2 raw diagnostic messages. 1164: Processed diagnostic messages (removed 0 due to limits, created 0 summary diagnostics for status page). 1165: Interpreted diagnostic messages (65ms). 1166: Uploading failed SARIF file ../codeql-failed-run.sarif 1167: ##[group]Uploading results 1168: Processing sarif files: ["../codeql-failed-run.sarif"] 1169: Validating ../codeql-failed-run.sarif 1170: Combining SARIF files using the CodeQL CLI 1171: Adding fingerprints to SARIF file. See https://docs.github.com/en/enterprise-cloud@latest/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning#providing-data-to-track-code-scanning-alerts-across-runs for more information. 1172: Uploading results 1173: Successfully uploaded results 1174: ##[endgroup] 1175: ##[group]Waiting for processing to finish 1176: Analysis upload status is pending. 1177: Analysis upload status is failed. 1178: ##[endgroup] 1179: CodeQL job status was configuration error. 1180: Sending status report for init-post step.

github-actions · 2025-04-25T16:26:34Z

Test Results

34 files - 9 34 suites - 9 18s ⏱️ -16s
358 tests - 38 358 ✅ - 38 0 💤 ±0 0 ❌ ±0
373 runs - 144 373 ✅ - 144 0 💤 ±0 0 ❌ ±0

Results for commit 73b9ace. ± Comparison against base commit 1e90f8a.

This pull request removes 80 and adds 41 tests. Note that renamed tests count towards both.


net.samyn.kapper.ExecuteTests ‑ [1] MYSQL
net.samyn.kapper.ExecuteTests ‑ [2] MSSQLSERVER
net.samyn.kapper.ExecuteTests ‑ [3] ORACLE
net.samyn.kapper.ExecuteTests ‑ [4] SQLITE
net.samyn.kapper.ExecuteTests ‑ [5] POSTGRESQL
net.samyn.kapper.QuerySingleTests ‑ [1] MYSQL
net.samyn.kapper.QuerySingleTests ‑ [2] MSSQLSERVER
net.samyn.kapper.QuerySingleTests ‑ [3] ORACLE
net.samyn.kapper.QuerySingleTests ‑ [4] SQLITE
…

net.samyn.kapper.internal.QueryParserTest ‑ [5] 

net.samyn.kapper.internal.SQLTypesConverterTest ‑ [10] LONGNVARCHAR, LONGNVARCHAR, net.samyn.kapper.internal.SQLTypesConverterTest$Companion$$Lambda$863/0x00007f1d4c501368@2424623b
net.samyn.kapper.internal.SQLTypesConverterTest ‑ [11] INSTANT, net.samyn.kapper.internal.SQLTypesConverterTest$Companion$$Lambda$734/0x00007f1d4c4afc78@279795ca
net.samyn.kapper.internal.SQLTypesConverterTest ‑ [11] LONGVARCHAR, LONGVARCHAR, net.samyn.kapper.internal.SQLTypesConverterTest$Companion$$Lambda$864/0x00007f1d4c501590@7eb2b116
net.samyn.kapper.internal.SQLTypesConverterTest ‑ [12] DATE, net.samyn.kapper.internal.SQLTypesConverterTest$Companion$$Lambda$735/0x00007f1d4c4ad3c0@6f8f4e21
net.samyn.kapper.internal.SQLTypesConverterTest ‑ [12] NCHAR, NCHAR, net.samyn.kapper.internal.SQLTypesConverterTest$Companion$$Lambda$865/0x00007f1d4c5017b8@73853fd
net.samyn.kapper.internal.SQLTypesConverterTest ‑ [13] LOCALDATE, net.samyn.kapper.internal.SQLTypesConverterTest$Companion$$Lambda$736/0x00007f1d4c4ad5e8@30623369
net.samyn.kapper.internal.SQLTypesConverterTest ‑ [13] NCLOB, NCLOB, net.samyn.kapper.internal.SQLTypesConverterTest$Companion$$Lambda$866/0x00007f1d4c5019e0@7f861b06
net.samyn.kapper.internal.SQLTypesConverterTest ‑ [14] LOCALDATETIME, net.samyn.kapper.internal.SQLTypesConverterTest$Companion$$Lambda$737/0x00007f1d4c4ada60@3932d0f4
net.samyn.kapper.internal.SQLTypesConverterTest ‑ [14] NVARCHAR, NVARCHAR, net.samyn.kapper.internal.SQLTypesConverterTest$Companion$$Lambda$867/0x00007f1d4c501c08@7f1abf51
…

♻️ This comment has been updated with latest results.

github-actions · 2025-04-25T16:54:18Z

Unit Tests

34 files 34 suites 16s ⏱️
358 tests 358 ✅ 0 💤 0 ❌
373 runs 373 ✅ 0 💤 0 ❌

Results for commit 6faf6e0.

♻️ This comment has been updated with latest results.

github-actions · 2025-04-25T16:54:19Z

Code Coverage

Total Project Coverage	98.70%

github-actions · 2025-04-25T17:06:07Z

POSTGRESQL Integration Tests

9 files 9 suites 16s ⏱️
18 tests 18 ✅ 0 💤 0 ❌
52 runs 52 ✅ 0 💤 0 ❌

Results for commit 6faf6e0.

♻️ This comment has been updated with latest results.

github-actions · 2025-04-25T17:06:07Z

SQLITE Integration Tests

9 files 9 suites 24s ⏱️
18 tests 18 ✅ 0 💤 0 ❌
52 runs 52 ✅ 0 💤 0 ❌

Results for commit 6faf6e0.

♻️ This comment has been updated with latest results.

github-actions · 2025-04-25T17:06:15Z

MSSQLSERVER Integration Tests

9 files 9 suites 22s ⏱️
18 tests 18 ✅ 0 💤 0 ❌
52 runs 52 ✅ 0 💤 0 ❌

Results for commit 6faf6e0.

♻️ This comment has been updated with latest results.

github-actions · 2025-04-25T17:06:18Z

MYSQL Integration Tests

9 files 9 suites 22s ⏱️
18 tests 18 ✅ 0 💤 0 ❌
52 runs 52 ✅ 0 💤 0 ❌

Results for commit 6faf6e0.

♻️ This comment has been updated with latest results.

github-actions · 2025-04-25T17:06:55Z

ORACLE Integration Tests

9 files 9 suites 23s ⏱️
18 tests 18 ✅ 0 💤 0 ❌
52 runs 52 ✅ 0 💤 0 ❌

Results for commit 6faf6e0.

♻️ This comment has been updated with latest results.

github-advanced-security · 2025-04-27T19:29:17Z

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

sonarqubecloud · 2025-04-27T19:41:32Z

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

Copilot AI review requested due to automatic review settings April 25, 2025 16:22

Copilot AI reviewed Apr 25, 2025

View reviewed changes

driessamyn force-pushed the optimise-build branch from ae5592b to a6844e3 Compare April 25, 2025 16:23

driessamyn force-pushed the optimise-build branch from d31bbe1 to 9cf592b Compare April 25, 2025 17:02

driessamyn force-pushed the optimise-build branch from 9cf592b to 2389674 Compare April 27, 2025 16:35

build: split integration test and run in parallel

76996ba

driessamyn force-pushed the optimise-build branch from ab29c29 to 76996ba Compare April 27, 2025 19:33

docs: add DB badges

6faf6e0

driessamyn merged commit 55a9011 into main Apr 27, 2025
15 checks passed

driessamyn deleted the optimise-build branch April 27, 2025 20:11

Conversation

driessamyn commented Apr 25, 2025

Uh oh!

qodo-free-for-open-source-projects Bot commented Apr 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

PR Code Suggestions ✨

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull Request Overview

Uh oh!

qodo-free-for-open-source-projects Bot commented Apr 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

CI Feedback 🧐

(Feedback updated until commit bef6dec)

Uh oh!

github-actions Bot commented Apr 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Test Results

Uh oh!

github-actions Bot commented Apr 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Unit Tests

Uh oh!

github-actions Bot commented Apr 25, 2025

Code Coverage

Uh oh!

github-actions Bot commented Apr 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

POSTGRESQL Integration Tests

Uh oh!

github-actions Bot commented Apr 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

SQLITE Integration Tests

Uh oh!

github-actions Bot commented Apr 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

MSSQLSERVER Integration Tests

Uh oh!

github-actions Bot commented Apr 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

MYSQL Integration Tests

Uh oh!

github-actions Bot commented Apr 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

ORACLE Integration Tests

Uh oh!

github-advanced-security AI commented Apr 27, 2025

Uh oh!

sonarqubecloud Bot commented Apr 27, 2025

Quality Gate passed

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

qodo-free-for-open-source-projects Bot commented Apr 25, 2025 •

edited

Loading

qodo-free-for-open-source-projects Bot commented Apr 25, 2025 •

edited

Loading

(Feedback updated until commit `bef6dec`)

github-actions Bot commented Apr 25, 2025 •

edited

Loading

github-actions Bot commented Apr 25, 2025 •

edited

Loading

github-actions Bot commented Apr 25, 2025 •

edited

Loading

github-actions Bot commented Apr 25, 2025 •

edited

Loading

github-actions Bot commented Apr 25, 2025 •

edited

Loading

github-actions Bot commented Apr 25, 2025 •

edited

Loading

github-actions Bot commented Apr 25, 2025 •

edited

Loading