#1027 (Jun 15, 2022, 12:05:03 AM)

	No changes.
	Started by upstream project jakarta-nosql build number 1027 originally caused by: Started by timer
	This run spent: 26 sec waiting; 8 min 13 sec build duration; 8 min 39 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.1 sec
Jakarta NoSQL	2 min 57 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	0.7 sec
communication-column	11 sec
communication-core	20 sec
communication-document	10 sec
communication-key-value	4.8 sec
communication-query	5.7 sec
mapping-api	0.49 sec
mapping-column	5.2 sec
mapping-core	5.7 sec
mapping-document	5.1 sec
mapping-key-value	4.7 sec
tck-parent	0.71 sec
communication-tck	0.52 sec
communication-tck-column	7.2 sec
communication-tck-core	5.4 sec
communication-tck-document	7 sec
communication-tck-key-value	4.6 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.7 sec
driver-tck-document	4.7 sec
driver-tck-key-value	4.3 sec
mapping-tck	0.58 sec
mapping-tck-column	6.7 sec
mapping-tck-core	4.2 sec
mapping-tck-document	6.4 sec
mapping-tck-entities	5.9 sec
mapping-tck-key-value	4.7 sec
mapping-tck-test	4.6 sec