Skip to content

[ci] Turn building and testing CppInterOp into reusable action #540

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

mcbarton
Copy link
Collaborator

Description

Please include a summary of changes, motivation and context for this PR.

This is the first in a series of PRs which should reduce some of the repetition in the ci. This PR turns building and testing CppInterOp into a reusable action. Specifically the action will only deal with native builds for now, but in future this action will expand to include the Emscripten build and test as well.

Fixes # (issue)

Type of change

Please tick all options which are relevant.

  • Bug fix
  • New feature
  • Requires documentation updates

Testing

Please describe the test(s) that you added and ran to verify your changes.

Checklist

  • I have read the contribution guide recently

@mcbarton mcbarton force-pushed the reusable-actions branch 3 times, most recently from 916a6f3 to f4a9d29 Compare March 26, 2025 17:19
Copy link

codecov bot commented Mar 26, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.46%. Comparing base (a9a865e) to head (83cf28f).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main     #540   +/-   ##
=======================================
  Coverage   75.46%   75.46%           
=======================================
  Files           9        9           
  Lines        3628     3628           
=======================================
  Hits         2738     2738           
  Misses        890      890           
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@vgvassilev
Copy link
Contributor

Don’t we need this in a separate repository?

@mcbarton
Copy link
Collaborator Author

mcbarton commented Mar 26, 2025

Don’t we need this in a separate repository?

@vgvassilev This will end up in the repo you created here https://github.com/compiler-research/ci-workflows eventually (at which they can be utilised across all the repos), but is better/easier in here for now until I can work out what all the actions need to be (I suspect that the actions I will make will get revised/refined over the coming few weeks).

@vgvassilev
Copy link
Contributor

So we keep it in the pr and once the pr is ready we close it and move it there?

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.

2 participants