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

INVALID: Framework: PR build showing missing test executable but no build failure #10841

Closed
bartlettroscoe opened this issue Aug 8, 2022 · 1 comment
Labels
PA: Framework Issues that fall under the Trilinos Framework Product Area resolved: invalid The development team feels the issue raised is invalid and will not address it type: bug The primary issue is a bug in Trilinos code or tests

Comments

@bartlettroscoe
Copy link
Member

bartlettroscoe commented Aug 8, 2022

Bug Report

@trilinos/framework, @jhux2, @csiefer2, @e10harvey

Description

There are cases where the PR build results posted to CDash show a not run test due to a missing test executable but no build failure. For example, for the builds:

showing:

image
...
image

for PR #10808, it showed the "Not Run" test ThyraEpetraAdapters_EpetraOperatorWrapper_UnitTests_MPI_4 with status Not Run link showing:

Unable to find required file: /scratch/trilinos/jenkins/ascic115/workspace/Trilinos_PR_clang-10.0.0/pull_request_test/packages/thyra/adapters/epetra/test/EpetraOperatorWrapper/ThyraEpetraAdapters_EpetraOperatorWrapper_UnitTests.exe

Well, how can that file be missing if there is no build error?

That suggests there is some type of framework problem here with how the build is being done, or how results are packaged up to send to CDash, or a problem with transmitting results to CDash, or a problem with how results are process and displayed on CDash.

I guarantee that is zero chance that I can reproduce this test as "Not Run" after running the "all" target without seeing a build error.

Steps to Reproduce

The fact that this strange state was reported in all three PR iterations for the same build suggests that this is a repeatable bug (but only in the autotester).

@bartlettroscoe bartlettroscoe added type: bug The primary issue is a bug in Trilinos code or tests PA: Framework Issues that fall under the Trilinos Framework Product Area labels Aug 8, 2022
@bartlettroscoe
Copy link
Member Author

FYI: This is likely due to using an old version of CMake before global error reporting was implemented. See #10893 (comment)

Closing as invalid.

@bartlettroscoe bartlettroscoe added the resolved: invalid The development team feels the issue raised is invalid and will not address it label Aug 18, 2022
@bartlettroscoe bartlettroscoe changed the title Framework: PR build showing missing test executable but no build failure INVALID: Framework: PR build showing missing test executable but no build failure Aug 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PA: Framework Issues that fall under the Trilinos Framework Product Area resolved: invalid The development team feels the issue raised is invalid and will not address it type: bug The primary issue is a bug in Trilinos code or tests
Projects
None yet
Development

No branches or pull requests

1 participant