Build #2,942

Cask Data Application Platform - Develop Build and Test

Build: #2942 failed Child of CDAP-DRC-4918

Build result summary


133 minutes
ecc70b28d6014f8265f84af78f745f8012510d30 ecc70b28d6014f8265f84af78f745f8012510d30
Total tests
Failing since
#2939 (Child of CDAP-DRC-4913)
Fixed in
#2943 (Child of CDAP-DRC-4919)


Code commits

Author Commit Message Commit date
Edwin Elia <> Edwin Elia <> ecc70b28d6014f8265f84af78f745f8012510d30 ecc70b28d6014f8265f84af78f745f8012510d30 Merge pull request #12247 from cdapio/feature-ui/CDAP-16886-run-ui-unit-tests
[CDAP-16886] add pom profile to run UI unit tests
albertshau <> albertshau <> 4313c35cb2475365e03b5a95a478343805bf9bdc 4313c35cb2475365e03b5a95a478343805bf9bdc Merge pull request #12252 from cdapio/feature/CDAP-16852-auto-join-macro-schemas
CDAP-16852 handle dynamic schemas in auto join
albertshau <> albertshau <> 7a67c119ca4920bb33a84af541adbbe00b368cc3 m 7a67c119ca4920bb33a84af541adbbe00b368cc3 CDAP-16852 handle dynamic schemas in auto join
Properly handle the case when the inputs into an auto-join stage
have null schemas due to the schema being unknown at deploy time,
usually because of macros.

In order to support this type of use case, added a way for a
plugin to specify the output schema in the JoinDefinition.
This should be used when the output schema cannot be derived
at deployment time due to macros. This is what the existing
Joiner currently requires the user to do for dynamic join
use cases.

For Spark, the implementation becomes significantly more difficult
due to the fact that the schema of each input stage needs to be
known in the Spark driver, in order to convert RDDs into

Added logic that derives the input schema using the output schema,
selected fields, and join keys. It is possible to derive
a usable schema when all the join keys are present in the final
output schema.
Edwin Elia <> Edwin Elia <> f875306754984d4d3ae4536520f197ce711ade29 m f875306754984d4d3ae4536520f197ce711ade29 [CDAP-16886] add pom profile to run UI unit tests


New test failures 1
Status Test View job Duration
Collapse Failed ReducibleAggregatorTest io.cdap.cdap.datapipeline.ReducibleAggregatorTest History
Unit Test Job < 1 sec
io.cdap.cdap.common.NamespaceCannotBeDeletedException: 'namespace:default' could not be deleted. Reason: Some programs are currently running in namespace 'namespace:default', please stop them before deleting namespace
	at io.cdap.cdap.test.TestBase.finish(
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(
	at java.lang.reflect.Method.invoke(
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(
(25 more lines...)
Existing test failures 1
Status Test Failing since View job Duration
java.util.concurrent.TimeoutException: Timeout occurred. Expected true but found false.
	at io.cdap.cdap.common.utils.Tasks.waitFor(
	at io.cdap.cdap.common.utils.Tasks.waitFor(
	at io.cdap.cdap.test.AbstractProgramManager.waitForRuns(
	at io.cdap.cdap.test.AbstractProgramManager.waitForRuns(
	at io.cdap.cdap.test.AbstractProgramManager.waitForRun(
	at io.cdap.cdap.datapipeline.ReducibleAggregatorTest.testFieldCountAgg(
	at io.cdap.cdap.datapipeline.ReducibleAggregatorTest.testFieldCountAgg(
(42 more lines...)
Fixed tests 2
Status Test Failing since View job Duration
Successful ReducibleAggregatorTest testFieldCountAgg History
Failing since build #2940 (Child of CDAP-DRC-4915) Unit Test Job 38 secs
Successful PreviewDataPipelineTest testMultiPhasePreview History
Failing since build #2940 (Child of CDAP-DRC-4915) Unit Test Job 48 secs

JIRA issues

Unknown Issue TypeCDAP-16852Could not obtain issue details from JIRA
Unknown Issue TypeCDAP-16886Could not obtain issue details from JIRA