Added protection on event slot creation in HiveWhiteBoard

So far the code could try to create a new event even if no slots were available. This was due to the fact that there was not count of free slots. The consequences where an exception out of range further down the road as the return code of the event creation was on top not checked properly. This adds a free slot counter in the white board

mentioned in merge request !480 (closed)

• [2017-11-15 11:03] Validation started with lhcb-gaudi-merge#302

Interesting that this double bookkeeping is needed now. Is there a chance to get it down again to have a centralized definition of slots rather than multiple counters?

Not really. There has always been 2 notions of slots corresponding to 2 indelendent resources : the slots in the event store for storing events, and the slots in the thread pool for scheduling algorithms. Only the latter one was checked, the former also needs to be. Actually if one could eventually be dropped, it's the second one, by letting TBB do it for us, but that's coming back to another discussion

yap. there is a reason why you can the whiteboard for the amount of free slots... anyhow, I agree with you that this is probably a topic for an independent discussion.

approved this merge request

assigned to @hegner

merged

mentioned in commit 8395a81c

changed milestone to %v30r0

added task scheduling label