#987 (May 9, 2022, 12:04:46 AM)

	No changes.
	Started by upstream project jakarta-nosql build number 987 originally caused by: Started by timer
	This run spent: 27 sec waiting; 4 min 27 sec build duration; 4 min 54 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.6 sec
Jakarta NoSQL	1 min 21 sec
nosql-column (didn’t run)
nosql-core (didn’t run)
nosql-document (didn’t run)
nosql-key-value (didn’t run)
spec	56 sec
communication-api	0.51 sec
communication-column	7.1 sec
communication-core	10 sec
communication-document	6.4 sec
communication-key-value	3.3 sec
communication-query	3.3 sec
mapping-api	0.4 sec
mapping-column	3.6 sec
mapping-core	3.2 sec
mapping-document	3.1 sec
mapping-key-value	2.8 sec
tck-parent	0.62 sec
communication-tck	0.53 sec
communication-tck-column	4 sec
communication-tck-core	3.1 sec
communication-tck-document	3.5 sec
communication-tck-key-value	2.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.44 sec
driver-tck-column	3.1 sec
driver-tck-document	2.9 sec
driver-tck-key-value	2.8 sec
mapping-tck	0.48 sec
mapping-tck-column	3.7 sec
mapping-tck-core	2.7 sec
mapping-tck-document	3.7 sec
mapping-tck-entities	3.3 sec
mapping-tck-key-value	2.8 sec
mapping-tck-test	2.5 sec