#1029 (Jun 17, 2022, 12:03:21 AM)

	No changes.
	Started by upstream project jakarta-nosql build number 1029 originally caused by: Started by timer
	This run spent: 16 sec waiting; 4 min 9 sec build duration; 4 min 25 sec 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.47 sec
Jakarta NoSQL	1 min 17 sec
nosql-column (didn’t run)
nosql-core (didn’t run)
nosql-document (didn’t run)
nosql-key-value (didn’t run)
spec	47 sec
communication-api	0.52 sec
communication-column	6.1 sec
communication-core	10 sec
communication-document	6.1 sec
communication-key-value	2.7 sec
communication-query	3.1 sec
mapping-api	0.38 sec
mapping-column	3 sec
mapping-core	3.1 sec
mapping-document	3.1 sec
mapping-key-value	2.6 sec
tck-parent	0.6 sec
communication-tck	0.53 sec
communication-tck-column	3.6 sec
communication-tck-core	3 sec
communication-tck-document	3.3 sec
communication-tck-key-value	2.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-tck	0.57 sec
driver-tck-column	2.7 sec
driver-tck-document	2.7 sec
driver-tck-key-value	2.5 sec
mapping-tck	0.4 sec
mapping-tck-column	3.4 sec
mapping-tck-core	2.6 sec
mapping-tck-document	3.2 sec
mapping-tck-entities	3.2 sec
mapping-tck-key-value	4.2 sec
mapping-tck-test	2.5 sec