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.

Sign up for GitHub

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

Jump to bottom

Test Piro_EpetraSolver_MPI_4 #826

Closed
bartlettroscoe opened this issue Nov 11, 2016 · 6 comments
Closed

Test Piro_EpetraSolver_MPI_4 #826

bartlettroscoe opened this issue Nov 11, 2016 · 6 comments
Labels
CLOSED_DUE_TO_INACTIVITY Issue or PR has been closed by the GitHub Actions bot due to inactivity. MARKED_FOR_CLOSURE Issue or PR is marked for auto-closure by the GitHub Actions bot. pkg: Piro type: bug The primary issue is a bug in Trilinos code or tests

Comments

@bartlettroscoe
Copy link
Member

CC: @trilinos/framework, @agsalin

Description:

The test Piro_EpetraSolver_MPI_4 has been failing in CI test for all recorded history as shown by:

which currently is only going back to 9/20. Yes, this test has been failing non-stop in CI testing for almost 2 full months!
@bartlettroscoe bartlettroscoe added type: bug The primary issue is a bug in Trilinos code or tests pkg: Piro labels Nov 11, 2016
@bartlettroscoe
Copy link
Member Author

This failing test is a blocker for #482 so I will disable it for the checkin-test.py script until it can be fixed.

bartlettroscoe added a commit to bartlettroscoe/Trilinos that referenced this issue Nov 11, 2016
@bartlettroscoe
Disable log-failing test Piro_EpetraSolver_MPI_4 in CI mode (trilinos…
af0d9f2 
…#826, trilinos#482)

This only impact CI builds, that is all.  Once this test is fixed, this can be
reverted.

See: trilinos#826, trilinos#482
bartlettroscoe added a commit to bartlettroscoe/Trilinos that referenced this issue Nov 11, 2016
@bartlettroscoe
Disable a bunch of failing Domi tests in CI builds (trilinos#826, tri…
9e75e2f 
…linos#482)

This only impacts CI builds.  Once these tests can be fixed then these
disables can be reverted.

See: trilinos#826, trilinos#482
@bartlettroscoe bartlettroscoe mentioned this issue Nov 12, 2016
Closed
bartlettroscoe added a commit to bartlettroscoe/Trilinos that referenced this issue Nov 12, 2016
@bartlettroscoe
Revert "Disable a bunch of failing Domi tests in CI builds (trilinos#826
a43d0d3 
, trilinos#482)"

This reverts commit 9e75e2f.
bartlettroscoe added a commit to bartlettroscoe/Trilinos that referenced this issue Nov 28, 2016
@bartlettroscoe
Disable log-failing test Piro_EpetraSolver_MPI_4 in CI mode (trilinos…
633544e 
…#826, trilinos#482)

This only impact CI builds, that is all.  Once this test is fixed, this can be
reverted.

See: trilinos#826, trilinos#482
bartlettroscoe added a commit that referenced this issue Nov 29, 2016
@bartlettroscoe
Merge branch 'cleanup-better-ci-build-482' into develop (#482, #362, #…
0acaa65 
…158, #831, #811, #826, #410)
rppawlo added a commit that referenced this issue Apr 19, 2017
@rppawlo
Piro: disable failing epetra test
d40a2eb 
Issue #826

Build/Test Cases Summary
Enabled Packages: Piro
Disabled Packages: PyTrilinos,Claps,TriKota
Enabled all Forward Packages
0) MPI_RELEASE_DEBUG_SHARED_PT => passed: passed=140,notpassed=0 (57.47 min)
Other local commits for this build/test group: 373697f
@rppawlo
Copy link
Contributor

rppawlo commented Apr 19, 2017

Disabled the epetra test completely and reverted Ross's original commit. The wrong vector space is being used. This looks like an issue in constructing the MV data structure for Dg/Dp.

@bartlettroscoe
Copy link
Member Author

This is ready to close, right?

@william76
Copy link
Contributor

@rppawlo

Has this ever been fixed? The Piro_EpetraSolver_MPI_4_DISABLE ON setting is still set up in testing -- just checking if it'd be safe to remove that guard or if that test is still considered failing?

@tjfulle tjfulle mentioned this issue Aug 23, 2019
Closed
@github-actions
Copy link

This issue has had no activity for 365 days and is marked for closure. It will be closed after an additional 30 days of inactivity.
If you would like to keep this issue open please add a comment and remove the MARKED_FOR_CLOSURE label.
If this issue should be kept open even with no activity beyond the time limits you can add the label DO_NOT_AUTOCLOSE.

@github-actions github-actions bot added the MARKED_FOR_CLOSURE Issue or PR is marked for auto-closure by the GitHub Actions bot. label Feb 20, 2021
@github-actions
Copy link

This issue was closed due to inactivity for 395 days.

@github-actions github-actions bot added the CLOSED_DUE_TO_INACTIVITY Issue or PR has been closed by the GitHub Actions bot due to inactivity. label Mar 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
CLOSED_DUE_TO_INACTIVITY Issue or PR has been closed by the GitHub Actions bot due to inactivity. MARKED_FOR_CLOSURE Issue or PR is marked for auto-closure by the GitHub Actions bot. pkg: Piro type: bug The primary issue is a bug in Trilinos code or tests
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@william76 @bartlettroscoe @rppawlo