#1024 (Jun 12, 2022, 12:07:46 AM)

	No changes.
	Started by upstream project jakarta-nosql build number 1024 originally caused by: Started by timer
	This run spent: 18 sec waiting; 9 min 42 sec build duration; 10 min total from scheduled to completion.
	Revision: 57170e631e084088edeea23b686db77df1bbda0f Repository: https://github.com/eclipse-ee4j/nosql refs/remotes/origin/master
	Test Result (no failures)

Module Builds

api-parent	0.99 sec
Jakarta NoSQL	2 min 16 sec
nosql-column (didn’t run)
nosql-core (didn’t run)
nosql-document (didn’t run)
nosql-key-value (didn’t run)
spec	1 min 44 sec
communication-api	1.1 sec
communication-column	11 sec
communication-core	20 sec
communication-document	10 sec
communication-key-value	4.6 sec
communication-query	5.4 sec
mapping-api	0.76 sec
mapping-column	4.9 sec
mapping-core	5.1 sec
mapping-document	5.2 sec
mapping-key-value	14 sec
tck-parent	0.62 sec
communication-tck	0.53 sec
communication-tck-column	7.5 sec
communication-tck-core	5.1 sec
communication-tck-document	6.4 sec
communication-tck-key-value	4.4 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.59 sec
driver-tck-column	5 sec
driver-tck-document	4.8 sec
driver-tck-key-value	8.4 sec
mapping-tck	0.52 sec
mapping-tck-column	6.5 sec
mapping-tck-core	43 sec
mapping-tck-document	6.3 sec
mapping-tck-entities	23 sec
mapping-tck-key-value	12 sec
mapping-tck-test	4 sec