Started 2 mo 2 days ago
Took 4 min 19 sec on basic-q3dmz

Build #761 (Sep 29, 2021, 12:04:30 AM)

No changes.

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

  • Started by timer

This run spent:

  • 30 sec waiting;
  • 4 min 19 sec build duration;
  • 4 min 49 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.54 sec
    Success Jakarta NoSQL1 min 31 sec
    Success spec50 sec
    Success communication-api0.49 sec
    Success communication-column4.7 sec
    Success communication-core11 sec
    Success communication-document4.5 sec
    Success communication-key-value2.4 sec
    Success communication-query3.7 sec
    Success mapping-api0.52 sec
    Success mapping-column2.4 sec
    Success mapping-core2.3 sec
    Success mapping-document2.4 sec
    Success mapping-key-value2.1 sec
    Success tck-parent0.52 sec
    Success communication-tck0.5 sec
    Success communication-tck-column2.6 sec
    Success communication-tck-core5.2 sec
    Success communication-tck-document2.5 sec
    Success communication-tck-key-value6.7 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.4 sec
    Success driver-tck-column2.1 sec
    Success driver-tck-document2.1 sec
    Success driver-tck-key-value2 sec
    Success mapping-tck0.59 sec
    Success mapping-tck-column2.7 sec
    Success mapping-tck-core2 sec
    Success mapping-tck-document2.6 sec
    Success mapping-tck-entities2.4 sec
    Success mapping-tck-key-value2.1 sec
    Success mapping-tck-test2.2 sec

    Upstream Builds