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

build(ci): Add breeze build and test job #11637

Closed
wants to merge 8 commits into from

Conversation

dreveman
Copy link
Collaborator

No description provided.

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Nov 23, 2024
@dreveman dreveman marked this pull request as draft November 23, 2024 17:58
Copy link

netlify bot commented Nov 23, 2024

Deploy Preview for meta-velox canceled.

Name Link
🔨 Latest commit bfdc9bd
🔍 Latest deploy log https://app.netlify.com/sites/meta-velox/deploys/6744db5ad8fde10008b50923

@dreveman dreveman force-pushed the github-ci branch 20 times, most recently from fa3b902 to 6b0eb84 Compare November 25, 2024 17:15
David Reveman added 2 commits November 25, 2024 12:27
This adds a flag to control whether breeze test fixtures should
be generated at build time or not.
@dreveman dreveman marked this pull request as ready for review November 25, 2024 17:33
@dreveman dreveman removed the request for review from majetideepak November 25, 2024 17:33
@dreveman dreveman requested a review from Yuhta November 25, 2024 17:33
@dreveman
Copy link
Collaborator Author

@Yuhta This fixes a number of build issues in breeze and introduces CI jobs to build and run all breeze tests on openmp and cuda. I can split this up into multiple PRs if we're not ready to add GPU jobs to CI at this time?

@dreveman
Copy link
Collaborator Author

@jon-rv @zytyz fyi

@assignUser
Copy link
Collaborator

assignUser commented Nov 25, 2024

Can we move this into it's own workflow so we can path filer on breeze so we only run it when necessary?

Edit: Just saw that this is rather quick but with the gpu runner being on the more expensive side I think it would still make sense to only run this when relevant files are changed (velox/experimenta/breeze/* and maybe CMake/* because you use velox_resolve_dependency?)

This builds and runs all Breeze unit tests using OpenMP.
This builds and runs all Breeze tests for CUDA.
@dreveman
Copy link
Collaborator Author

Can we move this into it's own workflow so we can path filer on breeze so we only run it when necessary?

Edit: Just saw that this is rather quick but with the gpu runner being on the more expensive side I think it would still make sense to only run this when relevant files are changed (velox/experimenta/breeze/* and maybe CMake/* because you use velox_resolve_dependency?)

Makes sense. Please take a look at latest version of the PR where I try to do that.

@dreveman
Copy link
Collaborator Author

@assignUser How does the latest version of this look to you?

Copy link
Collaborator

@assignUser assignUser left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Workflow looks good to me, thanks!

@assignUser
Copy link
Collaborator

Ah, one minor thing we could exclude breeze from the other builds trigger but that can be handled in a follow up.

@dreveman
Copy link
Collaborator Author

Ah, one minor thing we could exclude breeze from the other builds trigger but that can be handled in a follow up.

@assignUser That would be nice. We just need to make sure it's included in wave builds that use breeze. That's limited to a simple integration test today but is expected to increase in the near future. Maybe we exclude everything in breeze except the files that make up the header library. @Yuhta wdyt?

@Yuhta
Copy link
Contributor

Yuhta commented Nov 26, 2024

@dreveman Yes the breeze tests should only be run when breeze itself is changed. The integration with wave can be run when wave is changed though.

@Yuhta Yuhta added the ready-to-merge PR that have been reviewed and are ready for merging. PRs with this tag notify the Velox Meta oncall label Nov 26, 2024
@dreveman
Copy link
Collaborator Author

@dreveman Yes the breeze tests should only be run when breeze itself is changed. The integration with wave can be run when wave is changed though.

Ok, I'll create a PR for only running breeze tests when changing breeze code. My only concern is that if wave is using breeze and we don't run wave tests when making breeze changes then it will be pretty easy to break that integration.

@Yuhta
Copy link
Contributor

Yuhta commented Nov 27, 2024

@dreveman That's a good point, we should run breeze + wave tests when breeze is changed

@facebook-github-bot
Copy link
Contributor

@xiaoxmeng has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

@facebook-github-bot
Copy link
Contributor

@xiaoxmeng merged this pull request in 0d572d2.

TongWei1105 pushed a commit to TongWei1105/velox that referenced this pull request Dec 3, 2024
Summary: Pull Request resolved: facebookincubator#11637

Reviewed By: Yuhta

Differential Revision: D66560387

Pulled By: xiaoxmeng

fbshipit-source-id: b82a544d4f6a2e37abaa5bcc9dba4af4e7cba6c6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. Merged ready-to-merge PR that have been reviewed and are ready for merging. PRs with this tag notify the Velox Meta oncall
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants