#1499: Error in synchronisation after restriction ---------------------+------------------------------------------------------ Reporter: hinder | Owner: eschnett Type: defect | Status: closed Priority: major | Milestone: ET_2014_05 Component: Carpet | Version: development version Resolution: fixed | Keywords: ---------------------+------------------------------------------------------
Comment (by rhaas):
Well the tests *did* fail after Erik's changes but then the prolongation tests are not doing what normal thorn is supposed to do, ie they are not scheduling MoL_PostStep after the restrict. So data was regennerated (carpet-6-init-355-gb3bc3f5 "update test data").