fix: reducing space consumption in GitHub runners

[germa89]

Description

Last month we have seen a few errors regarding the runner running out of space.

Hence, let's reduce the disk footprint by removing non used files and using moving instead of copying on the logging steps.

Related link: actions/runner-images#10386

Issue linked

Related to #3751

Checklist

• I have visited and read Develop PyMAPDL.
• I have tested my changes locally
• I have added necessary documentation or updated existing documentation.
• I have followed the PyMAPDL coding style guidelines.
• I have added appropriate unit tests that also ensure the minimal coverage criteria.
• I have reviewed my changes before submitting this pull request.
• I have linked the issue or issues that are solved to the PR if any.
• I have assigned this PR to myself.
• I have marked this PR as draft if it is not ready to be reviewed yet.
• I have made sure that the title of my PR follows Commit naming conventions (e.g. feat: adding new MAPDL command)

Summary by Sourcery

Optimize GitHub runner disk space usage by reducing file operations and cleaning up temporary files

Bug Fixes:

• Reduce disk space usage in GitHub runners by minimizing file duplication

CI:

• Add steps to free up disk space before and after test runs
• Add flag to exclude logs from passed tests in pytest arguments

Chores:

• Replace file copy operations with move operations to reduce disk space consumption

[ansys-reviewer-bot]

Thanks for opening a Pull Request. If you want to perform a review write a comment saying:

@ansys-reviewer-bot review

[sourcery-ai]

Reviewer's Guide

To address GitHub runner space limitations, this PR implements changes across CI scripts and workflows. Log collection scripts (.sh files in "/.ci/") now utilize mv commands instead of cp to handle log files, preventing duplication. The "test-local.yml" workflow incorporates pre-test cleanup by removing the CodeQL directory and post-package installation cleanup via apt-get clean. Both testing workflows ("test-local.yml" and "test-remote.yml") now use a Pytest argument to suppress logs for passed tests, further reducing disk usage. The "test-local.yml" workflow also adds steps to output disk space information before and after tests.

File-Level Changes

Change	Details	Files
Switched from copying to moving files in log collection scripts to reduce disk footprint.	Replaced cp (copy) operations with mv (move) for various log, output, error, crash, and profiling files. Ensured target directory for profiling files is created before moving its contents.	/.ci/collect_mapdl_logs_remote.sh /.ci/collect_mapdl_logs_locals.sh
Implemented disk space saving measures and logging adjustments in GitHub workflows.	Added a pre-test step to delete the "/__t/CodeQL" directory. Modified apt install commands to include apt-get clean for removing cached package files. Added the "--report-log-exclude-logs-on-passed-tests" argument to PYTEST_ARGUMENTS to reduce log output. Integrated steps to display disk usage (df -h) before and after tests.	/.github/workflows/test-local.yml /.github/workflows/test-remote.yml
Documented the fix in the changelog.	Added a new changelog entry detailing the reduction in GitHub runner space consumption.	doc/changelog.d/3900.fixed.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @germa89 - I've reviewed your changes - here's some feedback:

• The duplicated 'Free Disk Space Before Build' step at the job's end might be redundant if the runner environment is ephemeral.
• Consider reducing the verbosity of the 'Show space consumption' step if its detailed output is primarily for initial debugging rather than routine monitoring.
• The PR description mentions 'using moving instead of copying' to reduce disk footprint, but this change doesn't appear in the provided diff.

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.28%. Comparing base (1b1b6b4) to head (a17d39f).
Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3900      +/-   ##
==========================================
- Coverage   88.29%   88.28%   -0.02%     
==========================================
  Files         187      187              
  Lines       14830    14830              
==========================================
- Hits        13094    13092       -2     
- Misses       1736     1738       +2     

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[germa89]

@sourcery-ai review

[germa89]

@pyansys-ci-bot LGTM

[pyansys-ci-bot]

✅ Approving this PR because germa89 said so in here 😬

[sourcery-ai]

Hey @germa89 - I've reviewed your changes - here's some feedback:

• Consider adding df -h logging to test-remote.yml for consistent space monitoring across workflows.
• Consider making log collection failures an error if these artifacts are critical for diagnostics, instead of only echoing a message.

Here's what I looked at during the review

• 🟡 General issues: 2 issues found
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}