8 commits

Author	SHA1	Message	Date
Abe Jellinek	20e75c3251	Remove Bluebird methods in concurrentCallerTest.js ... This is really messy and not ideal, but these tests were written for Bluebird Promise state inspection, and it's difficult to make them look nice without that being available.	2025-07-30 22:30:57 -04:00
Abe Jellinek	67d2e1cead	fx140: Asyncify/ESMify tests ... They seem to be succeeding when run individually, but failing when run as a whole. Not sure why yet.	2025-07-30 22:30:53 -04:00
Abe Jellinek	ece2b59700	fx140: More progress toward startup	2025-07-30 22:18:36 -04:00
Abe Jellinek	8f2bf50cec	Try to prevent ConcurrentCaller from failing CI (#4097)	2024-05-07 19:38:44 -04:00
Dan Stillman	e5d65f5936	Maybe reduce spurious errors in ConcurrentCaller test	2016-07-19 18:53:48 -04:00
Dan Stillman	05de47149f	Allow marking of errors as handled for Bluebird ... Set .handledRejection on an Error object to tell Bluebird that it's been handled and shouldn't be logged by onPossiblyUnhandledRejection().	2016-04-27 02:32:58 -04:00
Dan Stillman	bad9833896	Resolve caller.start() promise when passed functions finish ... Instead of waiting for all queued functions to finish	2015-11-11 02:14:30 -05:00
Dan Stillman	ee6793a9e6	ConcurrentCaller changes ... - Different constructor parameters - id property for logging - fcall() -> start() - add() to enqueue without starting - runAll() to run down queue and return promises for all current tasks - wait() to wait for all running tasks to finish	2015-10-29 02:57:42 -04:00