diff --git a/weed/worker/tasks/ec_vacuum/ec_vacuum_integration_test.go b/weed/worker/tasks/ec_vacuum/ec_vacuum_integration_test.go
deleted file mode 100644
index 72aa20768..000000000
--- a/weed/worker/tasks/ec_vacuum/ec_vacuum_integration_test.go
+++ /dev/null
@@ -1,31 +0,0 @@
-package ec_vacuum
-
-import (
-	"testing"
-
-	"github.com/stretchr/testify/assert"
-)
-
-// TestECVacuumGenerationZeroDowntime is a placeholder for integration testing
-// This test would require a full SeaweedFS cluster setup and is better suited
-// for end-to-end testing in a real environment
-func TestECVacuumGenerationZeroDowntime(t *testing.T) {
-	// This test validates the conceptual zero-downtime approach
-	// In a real integration test, this would:
-	// 1. Start a SeaweedFS cluster with multiple volume servers
-	// 2. Create EC volumes with test data
-	// 3. Start continuous read workload
-	// 4. Trigger EC vacuum with generation transition
-	// 5. Verify reads continue with zero downtime
-	// 6. Validate generation cleanup after grace period
-
-	t.Logf("✅ EC Vacuum Generation Zero Downtime Test Framework:")
-	t.Logf("  - Would test continuous reads during vacuum")
-	t.Logf("  - Would verify generation G→G+1 transition")
-	t.Logf("  - Would validate atomic activation")
-	t.Logf("  - Would test cleanup grace period")
-	t.Logf("  - Would ensure zero service interruption")
-
-	// For now, we rely on the unit tests to validate the core logic
-	assert.True(t, true, "Integration test framework ready")
-}