Started 1 mo 29 days ago
Took 4 min 13 sec on basic-6hbht

Build #764 (Oct 2, 2021, 12:04:51 AM)

No changes.

Started by upstream project jakarta-nosql build number 764
originally caused by:

  • Started by timer

This run spent:

  • 31 sec waiting;
  • 4 min 13 sec build duration;
  • 4 min 44 sec total from scheduled to completion.
Revision: 8cf4c76780f3d0e7e2d1ba75250483f8e4b96f04
Repository: https://github.com/eclipse-ee4j/nosql
  • refs/remotes/origin/master
Test Result (no failures)

    Module Builds

    Success api-parent0.61 sec
    Success Jakarta NoSQL1 min 29 sec
    Success spec45 sec
    Success communication-api0.74 sec
    Success communication-column4.9 sec
    Success communication-core8.1 sec
    Success communication-document4.3 sec
    Success communication-key-value2.4 sec
    Success communication-query4.2 sec
    Success mapping-api0.42 sec
    Success mapping-column2.4 sec
    Success mapping-core2.6 sec
    Success mapping-document2.4 sec
    Success mapping-key-value2.2 sec
    Success tck-parent0.55 sec
    Success communication-tck0.49 sec
    Success communication-tck-column3.4 sec
    Success communication-tck-core2.4 sec
    Success communication-tck-document3.7 sec
    Success communication-tck-key-value2.1 sec
     driver-tck (didn’t run)
     driver-tck-column (didn’t run)
     driver-tck-document (didn’t run)
     driver-tck-key-value (didn’t run)
    Success driver-tck0.44 sec
    Success driver-tck-column2.1 sec
    Success driver-tck-document2.2 sec
    Success driver-tck-key-value2 sec
    Success mapping-tck0.52 sec
    Success mapping-tck-column3 sec
    Success mapping-tck-core2.3 sec
    Success mapping-tck-document2.5 sec
    Success mapping-tck-entities2.4 sec
    Success mapping-tck-key-value2.1 sec
    Success mapping-tck-test1.9 sec

    Upstream Builds