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

Introduce Github Actions CI workflow #247

Merged
merged 2 commits into from
Jun 18, 2023
Merged

Introduce Github Actions CI workflow #247

merged 2 commits into from
Jun 18, 2023

Conversation

ad1tazi
Copy link
Contributor

@ad1tazi ad1tazi commented Jun 11, 2023

This commit addresses this issue #115 by adding a Github Actions CI workflow that compiles and tests the codebase on both Ubuntu 22.04 and macOS 12 Monterey. The workflow is triggered on pull requests against the main branch and on every push to the main branch.

To accommodate the resource constraints of the Github-hosted runners, a GGML_NITER environment variable is introduced, allowing tests to run within a reasonable time frame. test-grad0.c is modified to use this variable instead of GGML_NLOOP.

The workflow file includes:

  • A build strategy for both Ubuntu and MacOS.
  • An environment setup with variables GGML_NLOOP and GGML_NITER.
  • A step to limit the number of threads used by test2.c for efficient execution.
  • A typical build process with steps for environment creation, CMake configuration, building, and verbose testing with a timeout.

This commit integrates a Github Actions CI workflow that compiles and tests the codebase on both Ubuntu 22.04 and macOS 12 Monterey. The workflow is triggered on pull requests against the main branch and on every push to the main branch.

To accommodate the resource constraints of the Github-hosted runners, a `GGML_NITER` environment variable is introduced, allowing tests to run within a reasonable time frame. `test-grad0.c` is modified to use this variable instead of `GGML_NLOOP`.

The workflow file includes:

- A build strategy for both Ubuntu and MacOS.
- An environment setup with variables `GGML_NLOOP` and `GGML_NITER`.
- A step to limit the number of threads used by `test2.c` for efficient execution.
- A typical build process with steps for environment creation, CMake configuration, building, and verbose testing with a timeout.
@ggerganov ggerganov merged commit 886f1c8 into ggerganov:master Jun 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants