Add MacOS X tests

[jan-janssen]

Summary by CodeRabbit

• New Features

  • Expanded continuous integration testing to support both macOS and Ubuntu operating systems, enhancing compatibility.
  • Introduced a flexible matrix strategy for Python versions in the testing workflows, allowing for easier updates.

• Bug Fixes

  • Improved overall robustness of the testing process by ensuring broader coverage across different environments.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The recent changes enhance the GitHub Actions workflows for running unit tests by introducing a matrix strategy to support multiple operating systems and Python versions. This update allows testing on both macos-latest and ubuntu-latest, ensuring greater compatibility and flexibility in the CI/CD pipeline. The configuration now accommodates all specified Python versions in a more streamlined manner, improving the robustness and coverage of the testing environments.

Changes

Files	Change Summary
.github/workflows/unittests-mpich.yml, .github/workflows/unittests-openmpi.yml	Introduced a matrix strategy for operating systems and Python versions, allowing builds on macos-latest and ubuntu-latest, enhancing flexibility and coverage. runs-on now uses ${{ matrix.operating-system }}.

Poem

🌟 In fields of code where bunnies play,
We’ve spruced the tests in a grand new way!
Mac and Ubuntu, side by side,
With Python versions, we take great pride.
Hopping through CI, so robust and bright,
Our workflow dances in the morning light! 🐇✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between d2895e4 and f6197d0.

Files selected for processing (2)

• .github/workflows/unittests-mpich.yml (1 hunks)
• .github/workflows/unittests-openmpi.yml (1 hunks)

Additional comments not posted (4)

.github/workflows/unittests-mpich.yml (2)

13-13: LGTM!

The introduction of the matrix strategy for runs-on enhances the flexibility and coverage of the CI/CD pipeline.

---

16-27: LGTM!

The include matrix for operating systems and Python versions is correctly defined, ensuring comprehensive testing across different environments.

.github/workflows/unittests-openmpi.yml (2)

13-13: LGTM!

The introduction of the matrix strategy for runs-on enhances the flexibility and coverage of the CI/CD pipeline.

---

16-27: LGTM!

The include matrix for operating systems and Python versions is correctly defined, ensuring comprehensive testing across different environments.

[jan-janssen]

openmpi 5.0 bug - conda-forge/lammps-feedstock#207

OSError: dlopen(liblammps.dylib, 0x000A): symbol not found in flat namespace '_error_top'
--------------------------------------------------------------------------
prterun detected that one or more processes exited with non-zero status,
thus causing the job to be terminated. The first process to do so was:

   Process name: [prterun-Mac-1722615538655-5666@1,1] Exit code:    1
--------------------------------------------------------------------------