Verify environment variables in e2e test

[nojnhuh]

This change adds new steps to the e2e test to verify that each container in each pod contains logs showing the presence of any GPU_DEVICE_* environment variables. I checked that this at least catches where the CDI config is not setup properly, but didn't try all of the other possible failure modes here.

Fixes #57

[nojnhuh]

FYI I did sneak in this typo fix also.

[elezar]

@nojnhuh this is definitely an improvement, thanks.

Do you have a feel for the effort required to actually test the expected behaviour as called out in the README?

[nojnhuh]

Do you have a feel for the effort required to actually test the expected behaviour as called out in the README?

Do you mean checking at least as far as whether certain containers have the same or different GPUs allocated based on the environment variables defined in each container? And that the correct TimeSlicing/SpacePartitioning parameters are set? I could definitely do that, but it might get a little messy in a bash script.

[nojnhuh]

Do you have a feel for the effort required to actually test the expected behaviour as called out in the README?

Do you mean checking at least as far as whether certain containers have the same or different GPUs allocated based on the environment variables defined in each container? And that the correct TimeSlicing/SpacePartitioning parameters are set? I could definitely do that, but it might get a little messy in a bash script.

I pushed these changes in a new commit which I plan to squash if we're good with those changes.

/hold

[nojnhuh]

I'm very open to suggestions for ways to make this less of a copy-paste nightmare.

[nojnhuh]

@elezar This should be ready for another review, PTAL.

[elezar]

Thanks @nojnhuh.

This is quite verbose, but I suppose that's a side-effect of using bash instead of writing the tests in Ginkgo -- which is out of scope for this PR.

LGTM

[nojnhuh]

Squashed commits, didn't make any more changes in the process like the diff shows.

[elezar]

Lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: elezar, nojnhuh

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [elezar]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[nojnhuh]

Forgot to remove the hold here once I squashed.

/hold cancel

[pohly]

/lgtm

Based on #73 (review).