Adding support nightly cuopt-examples notebook testing

[ramakrishnap-nv]

Description

This adds testing for https://github.com/NVIDIA/cuopt-examples to nightly testing suite.

Issue

closes #334
closes #212

Checklist

• I am familiar with the Contributing Guidelines.
• Testing
  • New or existing tests cover these changes
  • Added tests
  • Created an issue to follow-up
  • NA
• Documentation
  • The documentation is up to date with these changes
  • Added new documentation
  • NA

[copy-pr-bot]

Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

[ramakrishnap-nv]

/ok to test ce40ff8

[ramakrishnap-nv]

/ok to test ce40ff8

[ramakrishnap-nv]

/ok to test 5d04191

[ramakrishnap-nv]

/ok to test 7968bab

[ramakrishnap-nv]

/ok to test 7cf79c0

[ramakrishnap-nv]

/ok to test 7cf79c0

[ramakrishnap-nv]

/ok to test 43e6418

[ramakrishnap-nv]

/ok to test 891408f

[ramakrishnap-nv]

/ok to test 65eac17

[ramakrishnap-nv]

/ok to test bba7a04

[ramakrishnap-nv]

@jameslamb may I get your review on this PR

[jameslamb]

This looks ok to me! I checked the logs (build link) and appreciate how informative they are, especially around the cleaning of ! commands which is the place where I think this is most likely to fail.

I think it's fine that the examples are coming from another repo since that repo is also in the NVIDIA org and controlled by similar security restrictions, branch protections, review standards, etc.

But you might in the future consider pinning to a specific commit of that repo instead of a branch ... otherwise, merges there could block all PR CI here.

And exciting that you were able to remove a bunch of unnecessary dependencies here!

[ramakrishnap-nv]

This looks ok to me! I checked the logs (build link) and appreciate how informative they are, especially around the cleaning of ! commands which is the place where I think this is most likely to fail.

I think it's fine that the examples are coming from another repo since that repo is also in the NVIDIA org and controlled by similar security restrictions, branch protections, review standards, etc.

But you might in the future consider pinning to a specific commit of that repo instead of a branch ... otherwise, merges there could block all PR CI here.

And exciting that you were able to remove a bunch of unnecessary dependencies here!

Yeah, I am planning to keep it only for nightly and remove it from PR for exact same reasons that I don't want to block PRs.

[ramakrishnap-nv]

/merge