Experimental Physics and
Industrial Control System

(Hmm, my email reply to the special [email protected] email
address did not seem to generate a comment here, so I'm adding the
comment again via the web UI.)

> I would like to make it easier for test authors to build safeguards
> like timeouts into their code.

Agreed.  The test case can know that a join should succeed within some
amount of time, and if it doesn't, it can fail the test explicitly with
a message saying exactly what went wrong.  This is better than a test
that just hangs.

I think it also has value in production code for a similar reason: if
the caller knows that the join should succeed within a certain amount
of time, it allows the caller to handle the case where it doesn't.  It
could log an error message, it could abort, it could do both, it could
try again, it could tell the thread to stop and then try again, etc.
-- 
https://code.launchpad.net/~epics-core/epics-base/+git/Com/+merge/361379
Your team EPICS Core Developers is subscribed to branch epics-base:7.0.

References:

Re: [Merge] ~epics-core/epics-base/+git/Com:thread-join into epics-base:7.0 Andrew Johnson via Core-talk

Navigate by Date:

Prev: Re: [Merge] ~epics-core/epics-base/+git/Com:thread-join into epics-base:7.0 Martin Konrad via Core-talk

Next: Re: [Merge] ~epics-core/epics-base/+git/Com:thread-join into epics-base:7.0 J. Lewis Muir via Core-talk

Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <2019>  2020  2021  2022  2023  2024 

Navigate by Thread:

Prev: Re: [Merge] ~epics-core/epics-base/+git/Com:thread-join into epics-base:7.0 Andrew Johnson via Core-talk

Next: Re: [Merge] ~epics-core/epics-base/+git/Com:thread-join into epics-base:7.0 Martin Konrad via Core-talk

Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <2019>  2020  2021  2022  2023  2024