Skip to content

Conversation

@ArangoGutierrez
Copy link
Collaborator

This pull request enhances the end-to-end (E2E) testing workflow by introducing a matrix strategy for testing multiple infrastructure variants (EOL and LATEST) and updating the associated configuration files. The changes aim to improve flexibility and maintainability in the E2E testing process.

Workflow Enhancements:

  • .github/workflows/e2e.yaml: Added a matrix strategy to test both EOL and LATEST infrastructure variants, with conditional execution to skip the EOL variant for pull request events. Updated job names, Holodeck configuration, and artifact names to reflect the variant being tested. [1] [2] [3]

Infrastructure Configuration Updates:

  • tests/e2e/infra/aws_EOL.yaml: Renamed from aws.yaml and modified to reflect the EOL variant setup by removing the imageId field.
  • tests/e2e/infra/aws_LATEST.yaml: Added a new configuration file for the LATEST infrastructure variant, specifying details such as instance type, region, ingress IP ranges, and NVIDIA driver installation.

@ArangoGutierrez ArangoGutierrez self-assigned this Jul 21, 2025
@ArangoGutierrez ArangoGutierrez added the testing issue/PR to fix/edit/create/enhance a project unit/e2e test label Jul 21, 2025

This comment was marked as outdated.

@coveralls
Copy link

coveralls commented Jul 21, 2025

Pull Request Test Coverage Report for Build 16420617111

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 35.023%

Totals Coverage Status
Change from base Build 16413509194: 0.0%
Covered Lines: 4463
Relevant Lines: 12743

💛 - Coveralls

aws_secret_access_key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
aws_ssh_key: ${{ secrets.AWS_SSH_KEY }}
holodeck_config: "tests/e2e/infra/aws.yaml"
holodeck_config: ${{ matrix.holodeck_file }}
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
holodeck_config: ${{ matrix.holodeck_file }}
holodeck_config: tests/e2e/infra/aws_${{ matrix.variant }}

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

done

- variant: EOL
holodeck_file: tests/e2e/infra/aws_EOL.yaml
- variant: LATEST
holodeck_file: tests/e2e/infra/aws_LATEST.yaml
Copy link
Member

Choose a reason for hiding this comment

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

We can remove this.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

done

exclude:
- variant: EOL
ispr: true
Copy link
Member

Choose a reason for hiding this comment

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

I would rather run against an older driver on PRs and LATEST on main.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I see, ok

@ArangoGutierrez ArangoGutierrez force-pushed the multiple_drivers_e2e branch 6 times, most recently from dfaf0f6 to 2ba86e7 Compare July 21, 2025 09:38
@ArangoGutierrez ArangoGutierrez changed the title [no-relnote] Add Multiple drivers to E2E matrix [no-relnote] Test multiple driver branches during E2E Jul 21, 2025
Signed-off-by: Carlos Eduardo Arango Gutierrez <eduardoa@nvidia.com>
Signed-off-by: Carlos Eduardo Arango Gutierrez <eduardoa@nvidia.com>
name: ginkgo-logs-${{ matrix.driver_branch }}
path: ginkgo.json
retention-days: 15
- name: Send Slack alert notification
Copy link
Member

Choose a reason for hiding this comment

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

Nit: Did we also want to include the driver branch in the Slack message?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Good idea!

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

done

Signed-off-by: Carlos Eduardo Arango Gutierrez <eduardoa@nvidia.com>
@ArangoGutierrez ArangoGutierrez requested a review from Copilot July 21, 2025 15:11
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This pull request enhances the end-to-end (E2E) testing workflow by introducing a matrix strategy to test multiple driver branches (550 and 575) instead of the previous single infrastructure variant approach. The changes include conditional execution logic to skip driver branch 575 for pull request events while allowing both branches to run on other events.

  • Added matrix strategy to test driver branches 550 and 575 with conditional execution
  • Created new driver branch-specific configuration file for branch 575
  • Updated job names, configuration paths, and artifact names to reflect the driver branch being tested

Reviewed Changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 1 comment.

File Description
tests/e2e/infra/driver-branch-575.yaml New configuration file for driver branch 575 with infrastructure specifications
.github/workflows/e2e.yaml Updated workflow to use matrix strategy for multiple driver branches with conditional execution
Comments suppressed due to low confidence (1)

.github/workflows/e2e.yaml:42

  • The matrix variable name 'is_pull_request' is misleading as it actually represents the inverse - whether it's NOT a pull request. Consider renaming to 'is_not_pull_request' or 'run_all_branches' for clarity.
        is_pull_request:

@ArangoGutierrez ArangoGutierrez merged commit 0920018 into NVIDIA:main Jul 21, 2025
16 checks passed
strategy:
matrix:
is_pull_request:
- ${{!( startsWith(github.ref, 'refs/pull/') )}}
Copy link
Member

Choose a reason for hiding this comment

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

One question: Why the !?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

testing issue/PR to fix/edit/create/enhance a project unit/e2e test

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants