https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79430
--- Comment #64 from Thomas Koenig <tkoenig at gcc dot gnu.org> --- (In reply to Jürgen Reuter from comment #63) > (In reply to Thomas Koenig from comment #62) > > I am currently at a loss how to proceed. > > Darn.... Did you apply the patch from PR79344? Yes. What I get if I do > `make check TESTS=mlm_matching_isr.run`. ========================================================== WHIZARD 2.4.1: tests/functional_tests/test-suite.log ========================================================== # TOTAL: 1 # PASS: 0 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 is FAIL: mlm_matching_isr.run ========================== Running script ./mlm_matching_isr.run | Writing log to 'mlm_matching_isr.log' | (Logging turned off.) | Preloaded model: SM | Process library 'mlm_matching_isr_lib': initialized | Preloaded library: mlm_matching_isr_lib | Reading commands from file '../../share/tests/functional_tests/mlm_matching_isr.sin' | Switching to model 'SM', scheme 'default' ?logging => true ?openmp_logging = false ?vis_history = false ?integration_timer = false ?pacify = true + IDENTIFIER <variable> = u ****************************************************************************** *** ERROR: This PDG-array variable is undefined at this point ****************************************************************************** | (WHIZARD run continues) + IDENTIFIER <variable> = d ****************************************************************************** *** ERROR: This PDG-array variable is undefined at this point ****************************************************************************** | (WHIZARD run continues) [user variable] quark = PDG() + IDENTIFIER <variable> = U ****************************************************************************** *** ERROR: This PDG-array variable is undefined at this point ****************************************************************************** | (WHIZARD run continues) + IDENTIFIER <variable> = D This occurred between 242780 (OK) and 242981 (not OK). Oh well... maybe I will bisect that one first, to find out what went wrong there, and then another bisection to find out which patch fixed that, and then....
