roystgnr

Ouch. The regression appears to be merely *triggered* by this patch; the old code could hypothetically end up failing on corners with multiple periodic boundaries as well, if the element...

> Fixing this may not be a trivial task though. IMHO fixing this one very-specific case would be trivial: if we added the simple "make sure we're on the correct...

Well that's a nice grab bag of CI regressions. `ERROR: Unable to locate a modulefile for 'cppunit'` in a `Fetch and Branch` is *definitely* not my fault. Going out on...

> Might not be a bad idea to start testing these more... that's up to you. The failure to test these more was on me - years ago we had...

I can reproduce the failure at 13 processors in `Parallel sweep`. In `dbg` mode I get: ``` fvkernels/fv_adapt.adapt: No index 133 in ghosted vector. fvkernels/fv_adapt.adapt: Vector contains [162,181) fvkernels/fv_adapt.adapt: And...

No way to be sure without bisecting. That parallel sweep test only gets run manually. Last run before this one was 5 months ago: https://civet.inl.gov/recipe_events/32443/

Hah, and fv_adapt.adapt failed then, too...

Previous run was 15 months ago, at which time fv_adapt tests didn't exist. So it's entirely possible that that test has *never* succeeded with 13 processors.

#3169 should have fixed a couple --disable-foo builds, but the distributed stuff is more of a problem; turns out my new triangulator code isn't quite as distributed-mesh-agnostic as I had...

> Kicking to see if the -np 4 failure is repeatable It is not...