Sorry for the false alarm.
These things do get reported - I was looking (grep) for the wrong string
in a huge log file.
** Changed in: epics-base
Status: New => Invalid
--
You received this bug notification because you are a member of EPICS
Core Developers, which is subscribed to EPICS Base.
Matching subscriptions: epics-core-list-subscription
https://bugs.launchpad.net/bugs/1945454
Title:
Callback queue overflows are not reported
Status in EPICS Base:
Invalid
Bug description:
We just learned (the hard way, of course) that callback queue
overflows are not reported anymore on stderr.
This may be a side effect of the introduction of the high water mark and overflow counter mechanism.
Serious as they may be, I would say the overflows should still be reported.
To manage notifications about this bug go to:
https://bugs.launchpad.net/epics-base/+bug/1945454/+subscriptions
- References:
- [Bug 1945454] [NEW] Callback queue overflows are not reported Ralph Lange via Core-talk
- Navigate by Date:
- Prev:
[Bug 1945454] [NEW] Callback queue overflows are not reported Ralph Lange via Core-talk
- Next:
epics-7.0 » mac - Build # 363 - Fixed! APS Jenkins 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:
[Bug 1945454] [NEW] Callback queue overflows are not reported Ralph Lange via Core-talk
- Next:
Build failed: EPICS Base 7 base-7.0-390 AppVeyor 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
|