Build #1,316

Builds CDAP artifacts and performs unit tests

Build: #1316 failed Child of CDAP-DRC-3831

Build result summary

Details

Completed
Duration
357 minutes
Labels
None
Revisions
CDAP Build
191281a07606f8e56e8756d9ff0be022e5f843a8 191281a07606f8e56e8756d9ff0be022e5f843a8
CDAP
bfb2a98051442808198984b15c7c78c222c82b08 bfb2a98051442808198984b15c7c78c222c82b08
Total tests
344
Fixed in
#1320 (Scheduled with changes by Tony Bach <tonybach@google.com> and tonybach <tonybach@google.com>)

No failed tests found, a possible compilation error occurred.

Responsible

No one has taken responsibility for this failure

Comments on Unit Tests

  1. Anonymous user

    Detected hung build state. Attempting to generate stack trace and terminate spawned sub-processes... - HungBuildKiller Plugin

  2. Anonymous user

    Detected hung build state. Attempting to generate stack trace and terminate spawned sub-processes.

Code commits

CDAP
Author Commit Message Commit date
albertshau <ashau@google.com> albertshau <ashau@google.com> bfb2a98051442808198984b15c7c78c222c82b08 bfb2a98051442808198984b15c7c78c222c82b08 Merge pull request #10170 from caskdata/feature/CDAP-13501-fix-flaky-program-lifecycle-tests
CDAP-13501 fix flaky run history tests
Albert Shau <ashau@desktobert.svl.corp.google.com> Albert Shau <ashau@desktobert.svl.corp.google.com> b1c395f0c657472d6f795cf77e572af4b3eabdd8 m b1c395f0c657472d6f795cf77e572af4b3eabdd8 CDAP-13501 fix flaky run history tests
Fix a race condition where a call to list run records is made first,
then calls to fetch individual run records are made and the results
compared. This is subject to race conditions where the cluster state
has changed. For example, when listing, a run record might be in the
DEPROVISIONING state. When it is individually fetched, it could be
in the DEPROVISIONED state. Instead of comparing entire run records,
just comparing run record program state, since that is really all that
is important for the test.

Also performing cleanup to remove duplicate code and to remove a bunch
of warnings.

JIRA issues

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

Error summary for Unit Tests

The job generated some errors, drill down into the full build log for more details.

warning: unable to rmdir hashing-tf-feature-generator: Directory not empty
warning: unable to rmdir logistic-regression-analytics: Directory not empty
warning: unable to rmdir naive-bayes-analytics: Directory not empty
warning: unable to rmdir skipgram-analytics: Directory not empty
warning: unable to rmdir tokenizer-analytics: Directory not empty
Cloning into 'condition-plugins'...
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=384m; support was removed in 8.0