Repository navigation
CI: Add AWS EFA testing infrastructure - #212
Conversation
12c9495 to
8bc4b14
Compare
8bc4b14 to
7eb100a
Compare
7eb100a to
97f1d0f
Compare
97f1d0f to
c5fd857
Compare
c5fd857 to
549d869
Compare
549d869 to
ef4d7b2
Compare
054e07e to
4edc040
Compare
4edc040 to
9dd8ab8
Compare
9dd8ab8 to
e229428
Compare
|
Hey, this is pretty cool! Just a couple comments: -We have nixlbench in the main repo now, it would be nice to see it integrated in some configuration (doesn't need to be right now) |
Hi, thanks for the feedback! |
pvijayakrish
left a comment
There was a problem hiding this comment.
PR looks good. Could you please share how the changes are tested and how the results from AWS batch will be reported back?
Introduce new testing capability for AWS Elastic Fabric Adapter environments through contrib/aws-efa module: - Shell script for running tests in AWS Batch environments - Configuration templates for AWS resources - Job definition for container specification - Documentation for usage in both CI and manual testing - Support for both C++ and Python testing"
Create new CI pipeline for AWS EFA validation: - Triggers on main branch pushes and pull requests - Runs both C++ and Python test variants - Uses AWS CLI container for executing tests - Includes proper credentials handling and cleanup - Outputs test results for CI verification"
Exclude AWS job definition from copyright header requirements since AWS Batch job definitions don't support custom fields like "copyright". Also AWS job definition does not contain proprietary code by any means.
Results propagation from AWSWhen the pod exits, we poll AWS for exit status. If the final state is FAILED, the script exits non-zero, so Github Actions marks the flow as failed. Testing doneThe changes are validated through the AWS EFA workflow, which provides end-to-end testing by executing NIXL tests on AWS infrastructure and reporting the results back to GitHub. Negative tests were also conducted to ensure robustness. |
What?
Add automated testing infrastructure for NIXL on AWS EFA environment via a new
contrib/aws-efa/module and GitHub Actions workflow.Why?
Ensure NIXL compatibility with AWS EFA environment by:
How?
Implement: