Failed to run hack/e2e-hostpath.sh with latest csi-test v3.0.0

[Madhu-1]

Updated version from v1.0.0-rc2 to v3.0.0 in hack/get-sanity.sh
Run ./hack/e2e-hostpath.sh failed with below error

./hack/e2e-hostpath.sh 
Downloading csi-test from https://github.com/kubernetes-csi/csi-test/releases/download/v3.0.0/csi-sanity-v3.0.0.linux.amd64.tar.gz

gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now
cp: cannot stat '/tmp/csi-sanity/csi-sanity': No such file or directory
make: *** No rule to make target 'hostpath'.  Stop.
sudo: _output/hostpathplugin: command not found
sudo: /home/mrajanna/workspace/bin/csi-sanity: command not found
kill: sending signal to 3643838 failed: No such process

as the csi-test is release doesn't container linux-amd64 tar file and make hostpath command is also not present in csi-driver-host-path

[Madhu-1]

cc @pohly

[pohly]

hack/get-sanity.sh cannot depend on pre-compiled binaries for recent csi-test release because those don't get published anymore. It would have to get and build the source code instead.

Building the hostpath driver probably also changed.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.