Cask Data Application Platform - Develop Build and Test

Build: #2192 was successful Child of CDAP-DRC-3823

Build result summary

Details

Completed
Duration
219 minutes
Labels
None
Agent
bamboo-agent08
Revision
9fd4cc20e159e429c0e82ccffc6e5ccd00c2646d 9fd4cc20e159e429c0e82ccffc6e5ccd00c2646d
Total tests
2402
First to pass since
#2188 (Child of CDAP-DRC-3816)

Code commits

Author Commit Message Commit date
albertshau <ashau@google.com> albertshau <ashau@google.com> 9fd4cc20e159e429c0e82ccffc6e5ccd00c2646d 9fd4cc20e159e429c0e82ccffc6e5ccd00c2646d Merge pull request #10173 from caskdata/feature/CDAP-13489-another-dynamic-partitioning-fix
CDAP-13489 another dynamic partioning test fix
Albert Shau <ashau@desktobert.svl.corp.google.com> Albert Shau <ashau@desktobert.svl.corp.google.com> 1dbbf9cd9fc9c35f3a2d4ab2faeebc4830d6f222 1dbbf9cd9fc9c35f3a2d4ab2faeebc4830d6f222 CDAP-13489 another dynamic partioning test fix
The previous fix can fail due to a race in program status
(CDAP-13296) where run records are not fetched in a single
transaction. If a run transitions state during a status call,
the status can incorrectly be returned as STOPPED.
Instead, just wait for the number of failed runs to increase,
which should always indicate that the run has completed.

Tests

Fixed tests 1
Status Test Failing since View job Duration
Successful ProgramLifecycleHttpHandlerTest testFlowHistory History
Failing since build #2191 (Child of CDAP-DRC-3822) Unit Test Job 5 secs

JIRA issues

IssueDescriptionStatus
Unknown Issue TypeCDAP-13296Could not obtain issue details from JIRA
Unknown Issue TypeCDAP-13489Could not obtain issue details from JIRA