You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Joe McDonnell (JIRA)" <ji...@apache.org> on 2018/11/19 20:10:00 UTC
[jira] [Commented] (IMPALA-2385) Update test scripts to support
repeated runs of end-to-end tests without restarting Impala
[ https://issues.apache.org/jira/browse/IMPALA-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16692197#comment-16692197 ]
Joe McDonnell commented on IMPALA-2385:
---------------------------------------
There are two distinct use cases here.
Endurance tests:
Run Impala for a long time with a broad selection of tests and verify overall durability and behavior. For example, verify that memory usage does not keep increasing. Verify that things don't hang. Verify that resources don't leak. Etc.
Targeted iteration of tests:
Run specific tests many times and observe failures (or verify that it doesn't fail). It is useful to be able to run only a small set of tests (i.e. specific end to end tests, etc). It is useful to be able to run until the first failure or to record multiple failures. Some effort may go into preserving logs for all test runs. Sometimes we want to do this for custom cluster tests (which is incompatible with keeping Impala running).
This is well-suited to having its own script that specifies a limited set of tests and allows certain modes of repeated execution. A simple first step is a script that runs a set of end to end tests and can repeat it a) until it fails b) a specific number of times c) for a specific time period. It should retain results for each run (see the --junit-xml and --result-log args to impala-py.test, which we use [in tests/run-tests.py|[https://github.com/apache/impala/blob/master/tests/run-tests.py#L57-L58].]
We should support both. However, there is no such thing as endurance tests for frontend tests, backend tests, or custom cluster tests. That leaves mainly end to end tests. So, from a practical perspective, the script that would work for the targeted case would also solve the endurance case. Let's focus on the script for the targeted iteration and then work in the endurance aspect later.
> Update test scripts to support repeated runs of end-to-end tests without restarting Impala
> ------------------------------------------------------------------------------------------
>
> Key: IMPALA-2385
> URL: https://issues.apache.org/jira/browse/IMPALA-2385
> Project: IMPALA
> Issue Type: Task
> Components: Infrastructure
> Affects Versions: Impala 2.2.4
> Reporter: Harrison Sheinblatt
> Priority: Major
> Labels: test-infra
>
> The intent of the job is to find crashes due to resource leaks or other stability issues by running the tests we have (which run in parallel) for an extended period of time.
> Currently, the job runs all tests, which include cluster tests that restart Impala, and it runs a loop in the driving bash script that forces a restart each iteration. These restarts must be removed.
> Further, it needs to be verified that no other test restarts Impala. Ideally the testing could also verify this automatically, but at least one manual check that there are no restarts must be made.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org