🤖 triggering CI on branch 'release-next' after synching from upstream/main #1860

	name: Func E2E Test

	on: [pull_request]

	jobs:
	test:
	name: E2E Test
	strategy:
	matrix:
	os: ["ubuntu-latest"]
	runs-on: ${{ matrix.os }}
	steps:
	- name: Set Environment Variables
	run: \|
	echo "KUBECONFIG=${{ github.workspace }}/hack/bin/kubeconfig.yaml" >> "$GITHUB_ENV"
	echo "PATH=${{ github.workspace }}/hack/bin:$PATH" >> "$GITHUB_ENV"
	- uses: actions/checkout@v4
	- uses: knative/actions/setup-go@main
	- name: Install Binaries
	run: ./hack/install-binaries.sh
	- name: Allocate Cluster
	run: \|
	attempt=0
	max_attempts=5
	until [ $attempt -ge $max_attempts ]
	do
	attempt=$((attempt+1))
	echo "------------------ Attempt $attempt ------------------"
	./hack/allocate.sh && break
	echo "------------------ failed, retrying... ------------------"
	if [ $attempt -ge $max_attempts ]; then
	echo "------------------ max # of retries reached, exiting ------------------"
	exit 1
	fi
	./hack/delete.sh
	echo "------------------ sleep for 5 minutes ------------------"
	sleep 300
	done
	echo "------------------ finished! attempt $attempt ------------------"
	- name: Local Registry
	run: ./hack/registry.sh
	- name: E2E Test
	run: make test-e2e
	- uses: codecov/codecov-action@v5
	with:
	files: ./coverage.txt
	flags: e2e-test

Provide feedback