Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update libmesh #15182

Merged
merged 3 commits into from May 15, 2020
Merged

Update libmesh #15182

merged 3 commits into from May 15, 2020

Conversation

lindsayad
Copy link
Member

@lindsayad lindsayad commented Apr 30, 2020

Summary of changes:

  • Make Elem::interior_parent always safe to call
  • Support shell preconditioning matrix in eigen system
  • Add dual shape functions
  • Add hash specialization for FEType
  • Added an API to retrieve eigenvalue
  • Fix an overzealous assertion in unpack_indexing
  • Update to MetaPhysicL 1.0.2
  • Make "NumericVector localize()" scalable if possible
  • Try appending to a VariableGroup in add_variables
  • Revert "Use push_parallel_packed_range in scatter_constraints"
  • Fixes for "make distcheck"
  • Don't undef or define MPI_REAL
  • Use push_parallel_packed_range in scatter_constraints
  • Use common m4 files from a submodule
  • Let user control sorting method used by BoundaryInfo::build_side_list()
  • Adding number of threads option to LibMeshInit.
  • QGaussLobatto: add fallback on regular Gauss quadrature
  • Add Tri::quality(SHAPE) metric.
  • Fixed valgrind issue with VecSetDM
  • Fix node unique_id in xda for libMesh 0.9.2
  • Use terser make_range() in place of IntRange where possible.
  • Add templated make_range() helper functions.
  • Don't renumber with parallel and non-contiguous numbering
  • AbaqusIO: Add support for "MASS" elements and "NODE" sidesets.
  • Respect empty variables in Nemesis_IO::write_nodal_data
  • More robust Partitioner::set_node_processor_ids
  • Introduce std::reference_wrapper for more examples
  • Use numerically stable Edge3::volume() algorithm
  • RB fix: fix to RBEIMConstruction
  • Multiple file support in meshtool
  • Small fix to RBConstruction
  • Introduce std::reference_wrapper in fem_system_ex1
  • Make Edge3::volume() calculation more robust.
  • Don't swap LIBS and CPPFLAGS
  • RBConstruction update to store an untransformed basis.
  • Smooth libmesh for PETSc-3.13
  • Fix flux error estimates when flux weights not in approximation space
  • Introduce std::reference_wrapper in fem_system_ex3
  • RBConstruction change: Small change to train_reduced_basis().
  • Update to post_process_elem_matrix_and_vector in RBConstruction
  • Bugfix in rb_construction_base.C
  • DofMap::add_constraint_row(): assert there is no diagonal entry
  • RBConstruction change to element post-processing
  • macrofice second-derivative quantities
  • Fixes for build_sphere(DistributedMesh)
  • Fix adjoint Dirichlet constraints with AMR
  • The 'extra_checks' parameter should match 'secure' for backwards comp…
  • FEMSystem assert should work with new casts
  • PetscSolverException: use specific error message if available
  • Add 'extra_checks' parameter to FEMap::inverse_map()
  • Add DirichletBoundary copy assignment operator.
  • FileSolutionHistory class
  • Testing unique_id uniqueness

Also, for conda, make sure we build libmesh without the gdb command.
Then I don't have to pass --without-gdb-backtrace every time.
Trying to spawn a gdb process takes forever. Nobody got time
for that.

Finally, in conda test and make sure we created a TIMPI library

Refs #14922

@lindsayad
Copy link
Member Author

@milljm I think that's all I need to do with conda right?

libmesh Outdated
@@ -1 +1 @@
Subproject commit 179e8c8c2dcbfcc01311bd6f5044a9534aa21584
Subproject commit f8e214a055c88f1917903367693ba5b6ce4aeb70
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Caution! This contains a submodule update

@milljm
Copy link
Member

milljm commented Apr 30, 2020

Correct!

@lindsayad
Copy link
Member Author

This https://civet.inl.gov/job/514885/ looks like a real failure. It seems that the current TIMPI hash checked into libMesh is on an orphaned branch (@roystgnr ), so the unreachable error makes sense. I actually don't understand why this only shows up in the non-conda builds.

@moosebuild
Copy link
Contributor

moosebuild commented Apr 30, 2020

Job Documentation on 149255b wanted to post the following:

View the site here

This comment will be updated on new commits.

@roystgnr
Copy link
Contributor

That TIMPI hash came in via libMesh/libmesh#2515 ...

Damn, this looks like my fault. I was futzing with TIMPI, was trying to push temporary tags to experiment with before submitting libMesh/libmesh#2534 , and must have unintentionally overwritten the previous tag and branch. Let me see what I can do.

@roystgnr
Copy link
Contributor

Give it a try now?

@moosebuild
Copy link
Contributor

Job Test timings on 5df2ade : invalidated by @lindsayad

@lindsayad
Copy link
Member Author

These failures look like they're caused by libMesh/libmesh#2491. Perhaps they need a fix like that in #15012?

@moosebuild
Copy link
Contributor

Job Code Coverage on 5df2ade wanted to post the following:

View code coverage site here

@lindsayad
Copy link
Member Author

Wow the valgrind memory errors in https://civet.inl.gov/job/514877/ are unreadable. Is this a conda artifact?

@lindsayad
Copy link
Member Author

Give it a try now?

This failed again. If I run git fetch; git fetch --tag in TIMPI I still don't see a corresponding branch or tag:

* acb414b 2020-04-30 Roy Stogner (tag: v1.1.1_bootstrapped) Add bootstrap output
* e9ef8f6 2020-04-30 Roy Stogner Don't ignore bootstrap output
* 8a09dd6 2020-04-30 Roy Stogner (tag: v1.1.1) Update NEWS
* b391e69 2020-04-30 Roy Stogner Bump up release number for autoconf refactoring
| * a27bd7e 2020-04-29 Roy Stogner (tag: v1.1.0_bootstrapped, up/branch_1.1.0) Add bootstrap output
| * a46b021 2020-04-29 Roy Stogner Don't ignore bootstrap output
|/  
*   64f6826 2020-04-29 roystgnr (tag: v1.1.0, up/master, up/HEAD) Merge pull request #30 from roystgnr/relative_submodule_path
|\  
| * 316ab2b 2020-04-29 Roy Stogner Use a relative path for submodules
|/  
*   7fb9089 2020-04-27 Alex Lindsay Merge pull request #29 from roystgnr/common_m4
|\  
| | * 9e59828 2020-04-24 Roy Stogner (up/branch_1.1.0_acsm) Add bootstrap output
| | * 85e2b62 2020-04-24 Roy Stogner Don't ignore bootstrap output
| |/  
| * 2e9e882 2020-04-24 Roy Stogner Remove obsolete macro
| * e683273 2020-04-24 Roy Stogner Use autoconf-submodule for ACSM+AX macros
|/  
| * 4054808 2020-04-21 Roy Stogner (HEAD) Add bootstrap output
| * 858381b 2020-04-21 Roy Stogner Don't ignore bootstrap output
|/  
* 157450a 2020-04-21 Roy Stogner Add missing header

@roystgnr
Copy link
Contributor

You might need git fetch --tag --force? Just look at the releases page - at least on Github, libMesh/TIMPI@4054808 is again the hash associated with v1.1.0_bootstrapped.

@roystgnr
Copy link
Contributor

These failures look like they're caused by libMesh/libmesh#2491. Perhaps they need a fix like that in #15012?

Let me see if I can replicate any of those.

@lindsayad
Copy link
Member Author

You have to have a branch pointer in order for the commit to be reachable:

(moose-boost) lindad@pop-os:~/projects/moose/libmesh/contrib/timpi(master)$ git fsck --unreachable up | grep commit.*4054808
Checking object directories: 100% (256/256), done.
Checking objects: 100% (465/465), done.
unreachable commit 4054808355ba2511247b83ac0a8aa0ce2a404e8b

@roystgnr
Copy link
Contributor

roystgnr commented May 1, 2020

Okay; branch_1.1.0 is now force pushed to connect to the tag too.

@moosebuild
Copy link
Contributor

Job Linux peacock testing on 5df2ade : invalidated by @lindsayad

should be able to fetch TIMPI now

@moosebuild
Copy link
Contributor

Job Test timings on 5df2ade : invalidated by @lindsayad

should be able to fetch TIMPI now

@moosebuild
Copy link
Contributor

moosebuild commented May 1, 2020

Job Test timings on 149255b wanted to post the following:

View timings here

This comment will be updated on new commits.

roystgnr added a commit to roystgnr/libmesh that referenced this pull request May 1, 2020
This was working fine in new libMesh, and in older libMesh, but not in
one of our intermediate file formats, which was breaking a CI test in
idaholab/moose#15182

Refs idaholab/moose#15193
@roystgnr
Copy link
Contributor

roystgnr commented May 1, 2020

libMesh/libmesh#2542 is merged now and should fix that unique_id test. No idea what's going on with those valgrind failures though.

@fdkong
Copy link
Contributor

fdkong commented May 1, 2020

libMesh/libmesh#2542 is merged now and should fix that unique_id test. No idea what's going on with those valgrind failures though.

#15202

libmesh Outdated
@@ -1 +1 @@
Subproject commit 179e8c8c2dcbfcc01311bd6f5044a9534aa21584
Subproject commit 61aef80a6e24f2ab1f3d7ec8668ca07eabd33fd4
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Caution! This contains a submodule update

@lindsayad
Copy link
Member Author

Yes, see now this will include the libmesh changes in all the conda targets 👍

@moosebuild
Copy link
Contributor

Job Test timings on 149255b : invalidated by @lindsayad

@moosebuild
Copy link
Contributor

All jobs on 149255b : invalidated by @lindsayad

Jason hates us

@@ -1 +1 @@
Subproject commit 179e8c8c2dcbfcc01311bd6f5044a9534aa21584
Subproject commit 30d38fc9b5bc608655d033117a8d5cb59c57ae4c
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Caution! This contains a submodule update

@moosebuild
Copy link
Contributor

Job Code Coverage on 149255b wanted to post the following:

View code coverage site here

@lindsayad
Copy link
Member Author

Oh yea beautiful pass

@fdkong
Copy link
Contributor

fdkong commented May 15, 2020

@lindsayad Do you want me to merge it right now?

@lindsayad
Copy link
Member Author

lindsayad commented May 15, 2020 via email

@fdkong
Copy link
Contributor

fdkong commented May 15, 2020

@milljm It is safe to get this in?

fdkong
fdkong previously requested changes May 15, 2020
Copy link
Contributor

@fdkong fdkong left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let us hold on for a moment

@fdkong fdkong requested a review from milljm May 15, 2020 16:50
@fdkong
Copy link
Contributor

fdkong commented May 15, 2020

I will let @milljm hit button on this one!

@milljm
Copy link
Member

milljm commented May 15, 2020

Lets make this change to the conda_build_config.cfg:

moose_petsc:
 - 3.12.5 build_2

The problem with this, will be that this version of PETSc isn't available yet. So we will need to wait until it is. Or merge into next, where it does exist.

This will fail PRs... but not in Next (as that is where Fande's PETSc update currently exists)
@@ -1 +1 @@
Subproject commit 179e8c8c2dcbfcc01311bd6f5044a9534aa21584
Subproject commit 30d38fc9b5bc608655d033117a8d5cb59c57ae4c
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Caution! This contains a submodule update

@milljm
Copy link
Member

milljm commented May 15, 2020

This should be merged anyway, as the error is due to PETSc 3.12.5 @ build_2 does not yet exist publicly (it exists in Next).

Or. We wait until Next, devel, master passes. Invalidate this, and then it will pass.

Copy link
Member

@milljm milljm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am merging this now, because libMesh passed, and Fande's PR passed (updating PETSc which this PR now includes). We don't want to create another PR with both updates.

@milljm milljm dismissed fdkong’s stale review May 15, 2020 17:28

We discussed off-list

@milljm milljm merged commit 10eaddb into idaholab:next May 15, 2020
cticenhour added a commit to cticenhour/moose that referenced this pull request Aug 23, 2023
cticenhour added a commit to cticenhour/moose that referenced this pull request Sep 6, 2023
cticenhour added a commit to cticenhour/moose that referenced this pull request Sep 19, 2023
cticenhour added a commit to cticenhour/moose that referenced this pull request Sep 20, 2023
cticenhour added a commit to cticenhour/moose that referenced this pull request Sep 21, 2023
oanaoana pushed a commit to oanaoana/moose that referenced this pull request Oct 19, 2023
oanaoana pushed a commit to oanaoana/moose that referenced this pull request Nov 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants