#988 (May 10, 2022, 12:04:52 AM)

	No changes.
	Started by upstream project jakarta-nosql build number 988 originally caused by: Started by timer
	This run spent: 28 sec waiting; 4 min 28 sec build duration; 4 min 56 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.5 sec
Jakarta NoSQL	1 min 17 sec
nosql-column (didn’t run)
nosql-core (didn’t run)
nosql-document (didn’t run)
nosql-key-value (didn’t run)
spec	51 sec
communication-api	0.48 sec
communication-column	10 sec
communication-core	9.8 sec
communication-document	6.1 sec
communication-key-value	2.7 sec
communication-query	3 sec
mapping-api	0.48 sec
mapping-column	3.2 sec
mapping-core	2.9 sec
mapping-document	3.1 sec
mapping-key-value	2.7 sec
tck-parent	0.6 sec
communication-tck	0.46 sec
communication-tck-column	3.4 sec
communication-tck-core	2.9 sec
communication-tck-document	3.5 sec
communication-tck-key-value	2.7 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.57 sec
driver-tck-column	2.8 sec
driver-tck-document	2.8 sec
driver-tck-key-value	2.7 sec
mapping-tck	0.57 sec
mapping-tck-column	3.2 sec
mapping-tck-core	2.6 sec
mapping-tck-document	3.4 sec
mapping-tck-entities	3.1 sec
mapping-tck-key-value	2.7 sec
mapping-tck-test	2.5 sec