search

trilinos / Trilinos

Primary repository for the Trilinos Project
https://trilinos.org/
Other
1.22k stars 569 forks source link

MueLu: Missing Directory /home/Trilinos/build Causing Automated Test Failures #13574

Closed ViNN280801 closed 2 weeks ago

ViNN280801 commented 2 weeks ago

Bug Report

Trilinos organization members, please @ mention the correct package team.
If you are not a member, please refer to https://github.com/trilinos/Trilinos/wiki/Trilinos-Package-Owners to mention the correct parties (because non-members cannot mention Github teams).

Description

When running automated tests on specific configurations, such as gcc10-openmpi416-EXPERIMENTAL, gcc830-serial-EXPERIMENTAL, cuda11-uvm-EXPERIMENTAL, and framework-tests-EXPERIMENTAL, the build fails due to a missing directory: /home/Trilinos/build.

Error Message

The following error message appears in the logs:

Error: An error occurred trying to start process '/usr/bin/bash' with working directory '/home/Trilinos/build'. No such file or directory

This suggests that the test environment is trying to use /home/Trilinos/build as the working directory, but this directory does not exist or is not being created during the setup process.

Expected Behavior

The automated tests should either:

  1. Automatically create the /home/Trilinos/build directory if it doesn't exist.
  2. Use a relative or configurable path that is guaranteed to be present in the testing environment.

This issue prevents Pull Requests from passing all checks in configurations that rely on this directory, blocking contributors from merging their changes.

Steps to Reproduce

  1. Do this:
    • Open a Pull Request or run the tests on configurations such as:
      • gcc10-openmpi416-EXPERIMENTAL
      • gcc830-serial-EXPERIMENTAL
      • cuda11-uvm-EXPERIMENTAL
      • framework-tests-EXPERIMENTAL
  2. Observe the failure with the error related to the missing directory.

Images

Image Image Image Image

Suggested Solution

Please consider updating the setup scripts for these test configurations to ensure the /home/Trilinos/build directory is created before attempting to use it. Alternatively, switching to a relative or dynamically generated path could also prevent this issue.

github-actions[bot] commented 2 weeks ago

Automatic mention of the @trilinos/muelu team

cgcgcg commented 2 weeks ago

@ViNN280801 The issue is that you don't have permissions to run the CI pipeline.

Initiating User ViNN280801 is not approved to run jobs on this machine.

I can kick it off once we have reviewed the proposed changes.