libMesh/libmesh: coverage diff

Base 41ae1d Head #4541 8e443e
Total Total +/- New
Rate 65.99% 65.99% +0.00% 100.00%
Hits 79526 79528 +2 3
Misses 40994 40994 - 0
Filename Stmts Miss Cover
src/mesh/distributed_mesh.C +2 0 +0.02%
TOTAL +2 0 +0.00%
code
coverage unchanged
code
coverage increased
code
coverage decreased
+
line added or modified

src/mesh/distributed_mesh.C

1122  
1123  
1124  
1125 +
1126  
1127  
1128 +
1129  
1130  
1131  
      // We communicate valid neighbor links for newly-redistributed
      // elements, but we may still have remote_elem links that should
      // be corrected but whose correction wasn't communicated.
      this->find_neighbors(/*reset_remote_elements*/ false,
                           /*reset_current_list*/ false /*non-default*/,
                           /*assert_valid*/ false,
                           /*check_non_remote*/ false /*non-default!*/);

      // Is this necessary?  If we are called from prepare_for_use(), this will be called
      // anyway... but users can always call partition directly, in which case we do need

src/mesh/unstructured_mesh.C

1007  
1008  
1009  
1010 +
1011  
1012  
1013  
            //
            // If we're only checking remote neighbors, after a
            // redistribution, then we'll skip the non-remote ones
            if ((element->neighbor_ptr(ms) == nullptr && check_non_remote) ||
                element->neighbor_ptr(ms) == remote_elem)
              {
                // Get the key for the side of this element.  Use the