#1030 (Jun 18, 2022, 12:04:53 AM)

	No changes.
	Started by upstream project jakarta-nosql build number 1030 originally caused by: Started by timer
	This run spent: 16 sec waiting; 7 min 19 sec build duration; 7 min 35 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	1.3 sec
Jakarta NoSQL	2 min 18 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 43 sec
communication-api	0.97 sec
communication-column	10 sec
communication-core	18 sec
communication-document	11 sec
communication-key-value	4.7 sec
communication-query	5.5 sec
mapping-api	0.76 sec
mapping-column	6 sec
mapping-core	5.1 sec
mapping-document	5.1 sec
mapping-key-value	4.7 sec
tck-parent	0.59 sec
communication-tck	0.53 sec
communication-tck-column	6.6 sec
communication-tck-core	5.2 sec
communication-tck-document	6.2 sec
communication-tck-key-value	4.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.54 sec
driver-tck-column	4.5 sec
driver-tck-document	4.5 sec
driver-tck-key-value	4.5 sec
mapping-tck	0.55 sec
mapping-tck-column	6.3 sec
mapping-tck-core	4.1 sec
mapping-tck-document	6.1 sec
mapping-tck-entities	5.6 sec
mapping-tck-key-value	4.8 sec
mapping-tck-test	4 sec