Subject: |
[Bug 1841634] [NEW] CP link triggers lost when record is async |
From: |
Andrew Johnson via Core-talk <[email protected]> |
To: |
[email protected] |
Date: |
Tue, 27 Aug 2019 16:49:38 -0000 |
Public bug reported:
>From Benjamin Franksen:
Here is a small self-contained database to reproduce this:
record(calcout,"input") {
field(CALC,"A<4?A+1:A")
field(INPA,"input")
field(ODLY,"1")
field(OUT,"input.A CA")
}
record(calcout,"output") {
field(ODLY,"1.5")
field(INPA,"input CPP")
field(CALC,"A")
field(TPRO,1)
}
record(calc,"check") {
field(INPA,"input CPP")
field(INPB,"output CPP")
field(CALC,"A==B")
}
Processing "input" (caput input.PROC 1) starts the test. The "check"
record should eventually settle to 1 (but doesn't).
With 7.0.3 I get this output:
scanOnce: dbProcess of 'output' # initial CPP processing
scanOnce: dbProcess of 'output'
scanOnce: dbProcess of Active 'output' with RPRO=0
scanOnce: dbProcess of 'output'
scanOnce: dbProcess of Active 'output' with RPRO=0
Note how this says "with RPRO=0".
And camonitor says:
franksen@tiber: ~ > camonitor input output check
input <undefined> 0 UDF INVALID
output 2019-08-27 16:02:16.106413 0
check 2019-08-27 16:02:16.106617 1
input 2019-08-27 16:02:26.498483 1
check 2019-08-27 16:02:26.498721 0
input 2019-08-27 16:02:27.493734 2
output 2019-08-27 16:02:27.993908 1
input 2019-08-27 16:02:28.489068 3
input 2019-08-27 16:02:29.484350 4
output 2019-08-27 16:02:29.984458 3
I think the difference in behavior between processing due to a CPP
input link versus processing due to a PP or CA output link is quite
surprising.
** Affects: epics-base
Importance: Wishlist
Status: Confirmed
** Affects: epics-base/7.0
Importance: Wishlist
Status: Confirmed
** Tags: codeathon
** Also affects: epics-base/7.0
Importance: Wishlist
Status: Confirmed
--
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/1841634
Title:
CP link triggers lost when record is async
Status in EPICS Base:
Confirmed
Status in EPICS Base 7.0 series:
Confirmed
Bug description:
From Benjamin Franksen:
Here is a small self-contained database to reproduce this:
record(calcout,"input") {
field(CALC,"A<4?A+1:A")
field(INPA,"input")
field(ODLY,"1")
field(OUT,"input.A CA")
}
record(calcout,"output") {
field(ODLY,"1.5")
field(INPA,"input CPP")
field(CALC,"A")
field(TPRO,1)
}
record(calc,"check") {
field(INPA,"input CPP")
field(INPB,"output CPP")
field(CALC,"A==B")
}
Processing "input" (caput input.PROC 1) starts the test. The "check"
record should eventually settle to 1 (but doesn't).
With 7.0.3 I get this output:
scanOnce: dbProcess of 'output' # initial CPP processing
scanOnce: dbProcess of 'output'
scanOnce: dbProcess of Active 'output' with RPRO=0
scanOnce: dbProcess of 'output'
scanOnce: dbProcess of Active 'output' with RPRO=0
Note how this says "with RPRO=0".
And camonitor says:
franksen@tiber: ~ > camonitor input output check
input <undefined> 0 UDF INVALID
output 2019-08-27 16:02:16.106413 0
check 2019-08-27 16:02:16.106617 1
input 2019-08-27 16:02:26.498483 1
check 2019-08-27 16:02:26.498721 0
input 2019-08-27 16:02:27.493734 2
output 2019-08-27 16:02:27.993908 1
input 2019-08-27 16:02:28.489068 3
input 2019-08-27 16:02:29.484350 4
output 2019-08-27 16:02:29.984458 3
I think the difference in behavior between processing due to a CPP
input link versus processing due to a PP or CA output link is quite
surprising.
To manage notifications about this bug go to:
https://bugs.launchpad.net/epics-base/+bug/1841634/+subscriptions
- Replies:
- [Bug 1841634] Re: CP link triggers lost when record is async Andrew Johnson via Core-talk
- [Bug 1841634] Re: CP link triggers lost when record is async mdavidsaver via Core-talk
- [Bug 1841634] Re: CP link triggers lost when record is async Andrew Johnson via Core-talk
- [Bug 1841634] Re: CP link triggers lost when record is async mdavidsaver via Core-talk
- [Bug 1841634] Re: CP link triggers lost when record is async Andrew Johnson via Core-talk
- [Bug 1841634] Re: CP link triggers lost when record is async mdavidsaver via Core-talk
- Navigate by Date:
- Prev:
[Bug 1841608] Re: logClient falsely sends error logs on all connections Dirk Zimoch via Core-talk
- Next:
[Bug 1841634] Re: CP link triggers lost when record is async Andrew Johnson 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 1841608] Re: logClient falsely sends error logs on all connections Martin Konrad via Core-talk
- Next:
[Bug 1841634] Re: CP link triggers lost when record is async Andrew Johnson 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
|