10d8e6f9

By: Tom Sydney Kerckhove <syd@cs-syd.eu>

Let STATUS decide busyness as well as TRANSP

A tentative event is now free.  TRANSP alone said whether the event would
consume time if it happened; STATUS says whether it is happening, and an
event nobody has agreed to does not take the time a definite one does.

No golden moves: none of the fixtures has a tentative event.  The change
is covered by 'pickedBusy' in PickSpec instead.

The four statuses that section 3.8.1.11 gives to a VTODO or a VJOURNAL
stay busy.  A VEVENT carrying one is not conforming and says nothing about
its time, so free would be the wrong way to be wrong.  They are enumerated
rather than swept into a catch-all so a new status has to be considered
here.  STATUS:CANCELLED stays busy for the same reason: such a component
never reaches rendering, so calling it free would claim a decision this
code does not make.

A declined ATTENDEE should count too and does not, because no setting says
which attendee is us; taking any attendee's refusal would make a
twenty-person meeting free because one of them could not come.

Total

1m16s

Created Started Finished

Time to Start Worker time Duration Time to finish Idle
Config 3m18s 0s 0s 3m19s 3m18s
Eval 3m43s 51s 51s 4m34s 24s
Build 4m29s 0s 0s 4m29s 0s
Suite 3m18s 52s 1m16s 4m34s 3m42s

Timeline

Config Eval Build Compressed gap
0s3m50s4m4m10s4m20s4m30s