Experimental Physics and Industrial Control System

Public bug reported:

There is a bug when adding records to an Event scan list. Adding a
record to an event scan list with a lower PHAS than any other previously
added record will end up putting it at the *end* of the list (not at the
beginning). Triggering the bug:

    $ cat test.db 
    record(ai, "SECOND") { field(EVNT, "E") field(SCAN, "Event") field(PHAS, "1") }
    record(ai, "FIRST")  { field(EVNT, "E") field(SCAN, "Event") field(PHAS, "0") }
    record(ai, "THIRD")  { field(EVNT, "E") field(SCAN, "Event") field(PHAS, "2") }

    $ softIoc -d test.db
    Starting iocInit
    ############################################################################
    ## EPICS R3.15.8-1+0~20200608134952.18+debian10~1.gbp3c2d35
    ## EPICS Base built Jun  8 2020
    ############################################################################
    iocRun: All initialization complete
    epics> scanpel
    Event "E"
     Priority Low
        SECOND                      
        FIRST                       
        THIRD                       
    epics>

The expected order is FIRST, SECOND, THIRD. I attached a patch (for
3.15.8) that I think fixes the issue. I found it in 3.15.8 but it seems
to affect 7.0 series as well.

** Affects: epics-base
     Importance: Undecided
         Status: New

** Patch added: "fix-event-scan-list.patch"
   https://bugs.launchpad.net/bugs/1899697/+attachment/5421868/+files/fix-event-scan-list.patch

-- 
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/1899697

Title:
  PHAS is not always respected when SCAN=Event

Status in EPICS Base:
  New

Bug description:
  There is a bug when adding records to an Event scan list. Adding a
  record to an event scan list with a lower PHAS than any other
  previously added record will end up putting it at the *end* of the
  list (not at the beginning). Triggering the bug:

      $ cat test.db 
      record(ai, "SECOND") { field(EVNT, "E") field(SCAN, "Event") field(PHAS, "1") }
      record(ai, "FIRST")  { field(EVNT, "E") field(SCAN, "Event") field(PHAS, "0") }
      record(ai, "THIRD")  { field(EVNT, "E") field(SCAN, "Event") field(PHAS, "2") }

      $ softIoc -d test.db
      Starting iocInit
      ############################################################################
      ## EPICS R3.15.8-1+0~20200608134952.18+debian10~1.gbp3c2d35
      ## EPICS Base built Jun  8 2020
      ############################################################################
      iocRun: All initialization complete
      epics> scanpel
      Event "E"
       Priority Low
          SECOND                      
          FIRST                       
          THIRD                       
      epics>

  The expected order is FIRST, SECOND, THIRD. I attached a patch (for
  3.15.8) that I think fixes the issue. I found it in 3.15.8 but it
  seems to affect 7.0 series as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/epics-base/+bug/1899697/+subscriptions

Replies:

[Bug 1899697] Re: PHAS is not always respected when SCAN=Event Andrew Johnson via Core-talk

[Bug 1899697] Re: PHAS is not always respected when SCAN=Event Andrew Johnson via Core-talk

[Bug 1899697] Re: PHAS is not always respected when SCAN=Event Martin Konrad via Core-talk

[Bug 1899697] Re: PHAS is not always respected when SCAN=Event Launchpad Bug Tracker via Core-talk

[Bug 1899697] Re: PHAS is not always respected when SCAN=Event Martin Konrad via Core-talk

[Bug 1899697] Re: PHAS is not always respected when SCAN=Event Andrew Johnson via Core-talk

[Bug 1899697] Re: PHAS is not always respected when SCAN=Event Dirk Zimoch via Core-talk

[Bug 1899697] Re: PHAS is not always respected when SCAN=Event Martin Konrad via Core-talk

Navigate by Date:

Prev: [Bug 1882120] Re: EPICS Open License - add to SPDX License List? Andrew Johnson via Core-talk

Next: [Bug 1899697] Re: PHAS is not always respected when SCAN=Event 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: Build failed: EPICS Base 7 base-7.0-90 AppVeyor via Core-talk

Next: [Bug 1899697] Re: PHAS is not always respected when SCAN=Event 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