Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add SQLTest #52293

Merged
merged 42 commits into from Aug 12, 2023
Merged

Add SQLTest #52293

merged 42 commits into from Aug 12, 2023

Conversation

alexey-milovidov
Copy link
Member

Changelog category (leave one):

  • Build/Testing/Packaging Improvement

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):

Add https://github.com/elliotchance/sqltest to CI to report the SQL 2016 conformance.

@robot-ch-test-poll2 robot-ch-test-poll2 added the pr-build Pull request with build/testing/packaging improvement label Jul 19, 2023
@robot-ch-test-poll2
Copy link
Contributor

robot-ch-test-poll2 commented Jul 19, 2023

This is an automated comment for commit 561e043 with description of existing statuses. It's updated for the latest CI running
The full report is available here
The overall status of the commit is 🔴 failure

Check nameDescriptionStatus
AST fuzzerRuns randomly generated queries to catch program errors. The build type is optionally given in parenthesis. If it fails, ask a maintainer for help🟢 success
CI runningA meta-check that indicates the running CI. Normally, it's in success or pending state. The failed status indicates some problems with the PR🟢 success
ClickHouse build checkBuilds ClickHouse in various configurations for use in further steps. You have to fix the builds that fail. Build logs often has enough information to fix the error, but you might have to reproduce the failure locally. The cmake options can be found in the build log, grepping for cmake. Use these options and follow the general build process🟢 success
Compatibility checkChecks that clickhouse binary runs on distributions with old libc versions. If it fails, ask a maintainer for help🟢 success
Docker image for serversThe check to build and optionally push the mentioned image to docker hub🟢 success
Fast testNormally this is the first check that is ran for a PR. It builds ClickHouse and runs most of stateless functional tests, omitting some. If it fails, further checks are not started until it is fixed. Look at the report to see which tests fail, then reproduce the failure locally as described here🟢 success
Flaky testsChecks if new added or modified tests are flaky by running them repeatedly, in parallel, with more randomization. Functional tests are run 100 times with address sanitizer, and additional randomization of thread scheduling. Integrational tests are run up to 10 times. If at least once a new test has failed, or was too long, this check will be red. We don't allow flaky tests, read the doc🟢 success
Install packagesChecks that the built packages are installable in a clear environment🟢 success
Integration testsThe integration tests report. In parenthesis the package type is given, and in square brackets are the optional part/total tests🔴 failure
Mergeable CheckChecks if all other necessary checks are successful🟢 success
Performance ComparisonMeasure changes in query performance. The performance test report is described in detail here. In square brackets are the optional part/total tests🟢 success
Push to DockerhubThe check for building and pushing the CI related docker images to docker hub🟢 success
SQLTestThere's no description for the check yet, please add it to tests/ci/ci_config.py:CHECK_DESCRIPTIONS🟢 success
SQLancerFuzzing tests that detect logical bugs with SQLancer tool🟢 success
SqllogicRun clickhouse on the sqllogic test set against sqlite and checks that all statements are passed🟢 success
Stateful testsRuns stateful functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc🟢 success
Stateless testsRuns stateless functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc🟢 success
Stress testRuns stateless functional tests concurrently from several clients to detect concurrency-related errors🟢 success
Style CheckRuns a set of checks to keep the code style clean. If some of tests failed, see the related log from the report🟢 success
Unit testsRuns the unit tests for different release types🟢 success
Upgrade checkRuns stress tests on server version from last release and then tries to upgrade it to the version from the PR. It checks if the new server can successfully startup without any errors, crashes or sanitizer asserts🟢 success

set -u
set -o pipefail

BINARY_TO_DOWNLOAD=${BINARY_TO_DOWNLOAD:="clang-16_debug_none_unsplitted_disable_False_binary"}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please, don't use the worst practices from performance tests. Binaries should be downloaded in advance and mounted into the container by a script from tests/ci

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok. I use copy-paste and ChatGPT to write Python. And when I'm using copy-paste, I'm trying to reuse the shortest code, so I have less amount to read.


run_log_path = os.path.join(temp_path, "run.log")
with open(run_log_path, "w", encoding="utf-8") as log:
with subprocess.Popen(
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TeePopen looks like a better class here

s3_prefix = f"{pr_info.number}/{pr_info.sha}/sqltest_{check_name_lower}/"
paths = {
"run.log": run_log_path,
"main.log": os.path.join(workspace_path, "main.log"),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just a side note, py3 has pathlib.Path class. It's much nicer in usage than the old os.path things

s3_helper = S3Helper()
for f in paths:
try:
paths[f] = s3_helper.upload_test_report_to_s3(paths[f], s3_prefix + f)
Copy link
Member

@Felixoid Felixoid Jul 21, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

by adding logs to TestResult you can skip this part


status = "success"
description = "See the report"
test_result = TestResult(description, "OK")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add logs and report files here

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok. I want to make a small working prototype first.
This check has limited use. It should exist; everything else we will address later (or never).

@Felixoid Felixoid self-assigned this Jul 21, 2023
@alexey-milovidov
Copy link
Member Author

@Felixoid currently it does not work due to

FAIL: test_get_changed_docker_images (docker_test.TestDockerImageCheck)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/ubuntu/actions-runner/_work/ClickHouse/ClickHouse/tests/ci/docker_test.py", line 99, in test_get_changed_docker_images
    self.assertEqual(images, expected)
AssertionError: Lists differ: [Dock[675 chars]est/sqltest,repo=clickhouse/sqltest,parent=cli[410 chars]est)] != [Dock[675 chars]est/stateful,repo=clickhouse/stateful-test,par[319 chars]est)]

First differing element 7:
Docke[20 chars]est/sqltest,repo=clickhouse/sqltest,parent=cli[13 chars]base)
Docke[20 chars]est/stateful,repo=clickhouse/stateful-test,par[25 chars]test)

First list contains 1 additional elements.
First extra element 11:
DockerImage(path=docker/test/unit,repo=clickhouse/unit-test,parent=clickhouse/stateless-test)

  [DockerImage(path=docker/docs/builder,repo=clickhouse/docs-builder,parent=None),
   DockerImage(path=docker/test/base,repo=clickhouse/test-base,parent=None),
   DockerImage(path=docker/docs/check,repo=clickhouse/docs-check,parent=clickhouse/docs-builder),
   DockerImage(path=docker/docs/release,repo=clickhouse/docs-release,parent=clickhouse/docs-builder),
   DockerImage(path=docker/test/fuzzer,repo=clickhouse/fuzzer,parent=clickhouse/test-base),
   DockerImage(path=docker/test/integration/base,repo=clickhouse/integration-test,parent=clickhouse/test-base),
   DockerImage(path=docker/test/keeper-jepsen,repo=clickhouse/keeper-jepsen-test,parent=clickhouse/test-base),
-  DockerImage(path=docker/test/sqltest,repo=clickhouse/sqltest,parent=clickhouse/test-base),
   DockerImage(path=docker/test/stateful,repo=clickhouse/stateful-test,parent=clickhouse/stateless-test),
   DockerImage(path=docker/test/stateless,repo=clickhouse/stateless-test,parent=clickhouse/test-base),
   DockerImage(path=docker/test/stress,repo=clickhouse/stress-test,parent=clickhouse/stateful-test),
   DockerImage(path=docker/test/unit,repo=clickhouse/unit-test,parent=clickhouse/stateless-test)]

@alexey-milovidov
Copy link
Member Author

What is the difference between images.json and docker_images.json?
They look almost identical, but not quite. And JSON does not support comments, unfortunately.

@alexey-milovidov
Copy link
Member Author

I found something strange, but didn't understand it: #33751

@alexey-milovidov
Copy link
Member Author

@Felixoid Now it is complete ..F.........

First differing element 7:
Docke[21 chars]st/sqltest,repo=clickhouse/sqltest,parent=clickhouse/test-base)
Docke[21 chars]st/sqltest,repo=clickhouse/sqltest,parent=clickhouse/test-base)

@Felixoid
Copy link
Member

Felixoid commented Aug 1, 2023

You shouldn't have used True for only_amd64

@alexey-milovidov
Copy link
Member Author

I thought Azure test was fixed...

@alexey-milovidov alexey-milovidov merged commit d059465 into master Aug 12, 2023
273 of 275 checks passed
@alexey-milovidov alexey-milovidov deleted the sqltest branch August 12, 2023 21:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr-build Pull request with build/testing/packaging improvement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants