#494: CarpetReduce tests nonstaggered and staggered fail with development version of Carpet ---------------------+------------------------------------------------------ Reporter: hinder | Owner: tbode Type: defect | Status: assigned Priority: major | Milestone: Component: Carpet | Version: Resolution: | Keywords: ---------------------+------------------------------------------------------
Comment (by hinder):
Testing reduction is probably something that wants to test inter-process communication, but we don't want a proliferation of too much test data. I wonder why there is gridfunction output in a reduction test anyway? Probably so that you can see when the test fails if it was due to the underlying grid functions or the reduction itself.
I would convert the test to use two processes and remove the one-process test (after the release).
By the way, I think that this is the last pair of test failures on Datura - when this is fixed we will have zero failures!