You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- increase max_time on a slow test
- restrict BC away from a test where it disagrees with SAM refs idaholab#408
- restrict moose away from a test where it passes the time step that BC / Pgh fail
We will likely remove the v |v| friction treatment and both will be consistent again
GiudGiud
added a commit
to joshuahansel/virtual_test_bed
that referenced
this issue
Jul 18, 2024
- increase max_time on a slow test
- restrict BC away from a test where it disagrees with SAM refs idaholab#408
- restrict moose away from a test where it passes the time step that BC / Pgh fail
We will likely remove the v |v| friction treatment and both will be consistent again
- loosen tolerances on other affected MSFR tests from this friction model change
- remove devel testing until getter simple issue is fixed
GiudGiud
added a commit
to joshuahansel/virtual_test_bed
that referenced
this issue
Jul 18, 2024
- increase max_time on a slow test
- restrict BC away from a test where it disagrees with SAM refs idaholab#408
- restrict moose away from a test where it passes the time step that BC / Pgh fail
We will likely remove the v |v| friction treatment and both will be consistent again
- loosen tolerances on other affected MSFR tests from this friction model change
- remove devel testing until getter simple issue is fixed
Bug Description
1st time step fails with BC, not with SAM
Steps to Reproduce
Run that input with recent BC and recent SAM, watch the first time step act differently
Impact
annoying for CI more than anything
The time steps taken are different but that does not necessarily make the results meaningfully different
The text was updated successfully, but these errors were encountered: