test(tablesdb): raise testDeleteStringTypeColumns poll timeout to 60s

Failed deterministically across both original-run attempts and both
rerun attempts of #12411 with `Failed asserting that 200 matches
expected 404` — column delete didn't propagate within 30s. The failing
PR doesn't touch TablesDB, columns, workers, or caching; this is the
known shared-mode CI delete-worker contention pattern. 60s matches the
migration polling default and is in line with the 240s used for
GraphQL attribute polling, both of which were raised for the same
underlying reason on parallel CI.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Jake BarnbyandClaude Opus 4.7 committed 2026-05-28 23:29:46 +12:00
1 parent b7d3c5ba77
commit 39e8fad97a
1 file changed
+4 -2
@@ -795,7 +795,9 @@ class DatabasesStringTypesTest extends Scope
$this->assertEquals(204, $deleteVarchar['headers']['status-code']);
// Poll until async deletion completes
// Poll until async deletion completes. Timeout raised to 60s to match
// the migration-polling and schema-polling defaults used elsewhere —
// shared-mode CI delete-worker contention can exceed the original 30s.
$this->assertEventually(function () use ($databaseId, $tableId) {
$response = $this->client->call(Client::METHOD_GET, '/tablesdb/' . $databaseId . '/tables/' . $tableId . '/columns/varchar_min', [
'content-type' => 'application/json',
@@ -803,6 +805,6 @@ class DatabasesStringTypesTest extends Scope
'x-appwrite-key' => $this->getProject()['apiKey'],
]);
$this->assertEquals(404, $response['headers']['status-code']);
}, 30000, 250);
}, 60000, 250);
}
}