Skip to content
Started 1 yr 10 mo ago
Took 7 min 2 sec on basic-fjmw3

#1013 (Jun 3, 2022, 12:03:44 AM)

No changes.

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

  • Started by timer

This run spent:

  • 29 sec waiting;
  • 7 min 2 sec build duration;
  • 7 min 32 sec total from scheduled to completion.
Revision: d84e398131f7384b20d5d9c1d5bbd3d5bbf1b17a
Repository: https://github.com/eclipse-ee4j/nosql
  • refs/remotes/origin/master
Test Result (no failures)

    Module Builds

     api-parent0.82 sec
     Jakarta NoSQL2 min 12 sec
     nosql-column (didn’t run)
     nosql-core (didn’t run)
     nosql-document (didn’t run)
     nosql-key-value (didn’t run)
     spec1 min 37 sec
     communication-api0.6 sec
     communication-column10 sec
     communication-core15 sec
     communication-document10 sec
     communication-key-value4.6 sec
     communication-query5.4 sec
     mapping-api0.49 sec
     mapping-column5.7 sec
     mapping-core5.1 sec
     mapping-document5.4 sec
     mapping-key-value4.6 sec
     tck-parent0.65 sec
     communication-tck0.6 sec
     communication-tck-column6.8 sec
     communication-tck-core5.3 sec
     communication-tck-document6.3 sec
     communication-tck-key-value4.5 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)
     driver-tck0.52 sec
     driver-tck-column4.8 sec
     driver-tck-document4.6 sec
     driver-tck-key-value4.5 sec
     mapping-tck0.5 sec
     mapping-tck-column6.9 sec
     mapping-tck-core3.8 sec
     mapping-tck-document6.2 sec
     mapping-tck-entities5.5 sec
     mapping-tck-key-value4.4 sec
     mapping-tck-test3.9 sec

    Downstream Builds