#1019 (Jun 8, 2022, 12:05:22 AM)

	No changes.
	Started by upstream project jakarta-nosql build number 1019 originally caused by: Started by timer
	This run spent: 24 sec waiting; 5 min 5 sec build duration; 5 min 29 sec total from scheduled to completion.
	Revision: 246c12949497eb8d4a56fe52849ba45aed0ebd6b Repository: https://github.com/eclipse-ee4j/nosql refs/remotes/origin/master
	Test Result (no failures)

Module Builds

api-parent	0.73 sec
Jakarta NoSQL	1 min 27 sec
nosql-column (didn’t run)
nosql-core (didn’t run)
nosql-document (didn’t run)
nosql-key-value (didn’t run)
spec	49 sec
communication-api	0.51 sec
communication-column	6.1 sec
communication-core	13 sec
communication-document	6.3 sec
communication-key-value	2.9 sec
communication-query	3.1 sec
mapping-api	0.42 sec
mapping-column	2.9 sec
mapping-core	3.1 sec
mapping-document	3 sec
mapping-key-value	2.6 sec
tck-parent	0.49 sec
communication-tck	0.49 sec
communication-tck-column	3.5 sec
communication-tck-core	2.8 sec
communication-tck-document	3.6 sec
communication-tck-key-value	2.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)
driver-tck	0.43 sec
driver-tck-column	2.8 sec
driver-tck-document	2.9 sec
driver-tck-key-value	2.6 sec
mapping-tck	0.44 sec
mapping-tck-column	3.4 sec
mapping-tck-core	2.5 sec
mapping-tck-document	3.3 sec
mapping-tck-entities	3.4 sec
mapping-tck-key-value	2.7 sec
mapping-tck-test	2.9 sec