#1020 (Jun 9, 2022, 12:04:42 AM)

	No changes.
	Started by upstream project jakarta-nosql build number 1020 originally caused by: Started by timer
	This run spent: 20 sec waiting; 5 min 15 sec build duration; 5 min 35 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	2.1 sec
Jakarta NoSQL	1 min 51 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 1 sec
communication-api	0.52 sec
communication-column	7.6 sec
communication-core	13 sec
communication-document	7.6 sec
communication-key-value	3.3 sec
communication-query	3.7 sec
mapping-api	0.69 sec
mapping-column	3.5 sec
mapping-core	3.6 sec
mapping-document	3.7 sec
mapping-key-value	3.1 sec
tck-parent	0.49 sec
communication-tck	0.45 sec
communication-tck-column	4.3 sec
communication-tck-core	3.2 sec
communication-tck-document	4.3 sec
communication-tck-key-value	2.9 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.4 sec
driver-tck-column	3.6 sec
driver-tck-document	3.5 sec
driver-tck-key-value	2.8 sec
mapping-tck	0.59 sec
mapping-tck-column	3.9 sec
mapping-tck-core	3 sec
mapping-tck-document	3.9 sec
mapping-tck-entities	3.6 sec
mapping-tck-key-value	2.8 sec
mapping-tck-test	2.6 sec