You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Joe McDonnell (Jira)" <ji...@apache.org> on 2020/12/24 01:32:00 UTC
[jira] [Resolved] (IMPALA-4203) Tests should run in a pipeline,
with each stage dependent upon the success of the former stage.
[ https://issues.apache.org/jira/browse/IMPALA-4203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe McDonnell resolved IMPALA-4203.
-----------------------------------
Fix Version/s: Not Applicable
Resolution: Won't Fix
> Tests should run in a pipeline, with each stage dependent upon the success of the former stage.
> -----------------------------------------------------------------------------------------------
>
> Key: IMPALA-4203
> URL: https://issues.apache.org/jira/browse/IMPALA-4203
> Project: IMPALA
> Issue Type: Improvement
> Components: Infrastructure
> Affects Versions: Impala 2.7.0
> Reporter: David Knupp
> Priority: Major
> Fix For: Not Applicable
>
>
> Currently, our test execution proceeds in the order of:
> * backend tests
> * frontend tests
> * system, or end-to-end tests
> If any of these logical stages produces a test failure, the Jenkins job should stop. However, we seem to continue to execute subsequent stages even when previous stages have failed. At the very least, we know that end-to-end tests run, even after BE tests have failed.
> It's a basic tenet of software testing that if unit tests fail, those need to be triaged and fixed before any further testing can be done.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)