Set the Ginkgo timeout to 5 hours.

Signed-off-by: Xun Jiang <blackpigletbruce@gmail.com>

test/Makefile

@@ -169,6 +169,7 @@ run-e2e: ginkgo
 		-v \
 		--junit-report report.xml \
 		--label-filter="$(GINKGO_LABELS)" \
+		--timeout=5h \
 		./e2e \
 		-- $(COMMON_ARGS) \
 		--upgrade-from-velero-cli=$(UPGRADE_FROM_VELERO_CLI) \
@@ -208,6 +209,7 @@ run-perf: ginkgo
 		-v \
 		--junit-report report.xml \
 		--label-filter="$(GINKGO_LABELS)" \
+		--timeout=5h \
 		./perf \
 		-- $(COMMON_ARGS) \
 		--nfs-server-path=$(NFS_SERVER_PATH) \

test/e2e/README.md

@@ -255,7 +255,7 @@ E2E tests can be run with specific cases to be included and/or excluded using th
 
 1. Run Velero tests with specific cases to be excluded:
     ```bash
-    GINKGO_LABELS="!Scale || !Schedule || !TTL || !(Upgrade && Restic) || !(Migration && Restic)" \
+    GINKGO_LABELS="!(Scale || Schedule || TTL || (Upgrade && Restic) || (Migration && Restic))" \
     CLOUD_PROVIDER=aws \
     BSL_BUCKET=example-bucket \
     CREDS_FILE=/path/to/aws-creds \