#989 (May 11, 2022, 12:04:52 AM)

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

Module Builds

api-parent	0.57 sec
Jakarta NoSQL	1 min 20 sec
nosql-column (didn’t run)
nosql-core (didn’t run)
nosql-document (didn’t run)
nosql-key-value (didn’t run)
spec	57 sec
communication-api	0.66 sec
communication-column	6.7 sec
communication-core	10 sec
communication-document	6.6 sec
communication-key-value	2.9 sec
communication-query	3.3 sec
mapping-api	0.46 sec
mapping-column	3.1 sec
mapping-core	3.2 sec
mapping-document	3.3 sec
mapping-key-value	2.9 sec
tck-parent	0.55 sec
communication-tck	0.43 sec
communication-tck-column	3.6 sec
communication-tck-core	3.4 sec
communication-tck-document	3.9 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.51 sec
driver-tck-column	3 sec
driver-tck-document	3 sec
driver-tck-key-value	2.7 sec
mapping-tck	0.53 sec
mapping-tck-column	3.6 sec
mapping-tck-core	2.7 sec
mapping-tck-document	3.4 sec
mapping-tck-entities	3.3 sec
mapping-tck-key-value	2.7 sec
mapping-tck-test	2.8 sec