You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: slice/README.md
-23Lines changed: 0 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -117,29 +117,6 @@ is manually re-applied afterwards.
117
117
118
118
More information can be found via the [Kubebuilder Documentation](https://book.kubebuilder.io/introduction.html)
119
119
120
-
## Running e2e tests using custom build
121
-
```shell
122
-
make kind-image-build test-e2e
123
-
```
124
-
125
-
## Attaching e2e tests to an existing kind cluster
126
-
You can use the following approach to start up a kind cluster and then run e2e tests from commandline or VSCode,
127
-
attaching them to the existing cluster. For example, suppose you want to test some of the multikueue-e2e tests.
128
-
129
-
Run `make kind-image-build test-e2e E2E_RUN_ONLY_ENV=true` and wait for the `Do you want to cleanup? [Y/n] ` to appear.
130
-
131
-
The cluster is ready, and now you can run tests from another terminal:
132
-
```shell
133
-
./bin/ginkgo -focus "JobSet (when )?Creating a JobSet it should create Slice based on created Workload with TPU topology 4x4x4, TPU topology 4 and parallelism 16" -v ./test/e2e/...
134
-
```
135
-
or from VSCode.
136
-
137
-
## Quick rebuild Kueue in e2e tests
138
-
If the `E2E_RUN_ONLY_ENV` variable is set, you can rebuild **only the Kueue image** without needing to rebuild the entire cluster.
139
-
```shell
140
-
make kind-image-build test-e2e E2E_RUN_ONLY_ENV=true E2E_RUN_ONLY_SLICE=true
0 commit comments