#1006 (May 28, 2022, 12:08:12 AM)

	No changes.
	Started by upstream project jakarta-nosql build number 1006 originally caused by: Started by timer
	This run spent: 19 sec waiting; 5 min 21 sec build duration; 5 min 41 sec total from scheduled to completion.
	Revision: 1ae878bc1657729d7f3d9d84310cd7d93e7acf5e Repository: https://github.com/eclipse-ee4j/nosql refs/remotes/origin/master
	Test Result (no failures)

Module Builds

api-parent	0.82 sec
Jakarta NoSQL	1 min 28 sec
nosql-column (didn’t run)
nosql-core (didn’t run)
nosql-document (didn’t run)
nosql-key-value (didn’t run)
spec	55 sec
communication-api	0.59 sec
communication-column	6.3 sec
communication-core	10 sec
communication-document	36 sec
communication-key-value	2.9 sec
communication-query	3.2 sec
mapping-api	8.1 sec
mapping-column	3.8 sec
mapping-core	3.2 sec
mapping-document	3 sec
mapping-key-value	2.6 sec
tck-parent	0.49 sec
communication-tck	0.55 sec
communication-tck-column	3.4 sec
communication-tck-core	3 sec
communication-tck-document	3.5 sec
communication-tck-key-value	4.8 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.39 sec
driver-tck-column	2.9 sec
driver-tck-document	3.1 sec
driver-tck-key-value	2.8 sec
mapping-tck	0.46 sec
mapping-tck-column	5.7 sec
mapping-tck-core	2.5 sec
mapping-tck-document	3.3 sec
mapping-tck-entities	3.1 sec
mapping-tck-key-value	2.9 sec
mapping-tck-test	2.5 sec