| 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 <2022> 2023 2024 2025 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 <2022> 2023 2024 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: Bus errors accessing VME with base 7.0.6.1 and latest synApps modules |
| From: | Michael Davidsaver via Tech-talk <tech-talk at aps.anl.gov> |
| To: | Mark Rivers <rivers at cars.uchicago.edu>, Torsten Bögershausen <Torsten.Bogershausen at ess.eu>, Benjamin Franksen <benjamin.franksen at helmholtz-berlin.de> |
| Cc: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
| Date: | Wed, 1 Jun 2022 12:03:23 -0700 |
On 6/1/22 10:54, Mark Rivers wrote:
Both of those commits were part of this PR https://github.com/epics-base/epics-base/pull/99 <https://github.com/epics-base/epics-base/pull/99> One of the comments on that PR (January 27, 2021) was: We expect to be nervous about this change because of the complex area it's working in, so we will merge it /after/ the next release which should be before the Codeathon in March, but we don't see anything obviously wrong with it.
This PR was recognized as having a high risk change of regression. The code involved is some of the most complex in Base. (Try to follow all of the possible paths through dbGet() ) This change was judged to be worthwhile since it actually reduces that complexity. Sadly, we don't get many PRs with a net reduction in source line count. Merging after the 7.0.5 release, and before the 2021 codeathon, was an attempt to mitigate this risk by maximizing the amount of testing before 7.0.6. Unfortunately, this seems not to have been enough.