[Bug 1899697] Re: PHAS is not always respected when SCAN=Event

[Andrew Johnson via Core-talk <core-talk at aps.anl.gov>]

** Changed in: epics-base
       Status: New => Triaged

** Changed in: epics-base
   Importance: Undecided => Medium

** Also affects: epics-base/7.0
   Importance: Medium
       Status: Triaged

** Also affects: epics-base/3.15
   Importance: Undecided
       Status: New

** Changed in: epics-base/7.0
    Milestone: None => 7.0.5

** Changed in: epics-base/3.15
    Milestone: None => 3.15.9

** Changed in: epics-base/3.15
       Status: New => Triaged

** Changed in: epics-base/3.15
   Importance: Undecided => Medium

-- 
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:
  Triaged
Status in EPICS Base 3.15 series:
  Triaged
Status in EPICS Base 7.0 series:
  Triaged

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