Closed Bug 1518896 Opened 6 years ago Closed 6 years ago

Tests are failing due to us having too many testing containers

Categories

(Taskcluster :: Services, enhancement)

Product:
Taskcluster
Component:
Services
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1533937

People

(Reporter: bstack, Unassigned)

Details

[0] is an example. We can fix this temporarily by using pagination in that test case but eventually that will slow us down to a very slow test. We should have some way of cleaning up old testing tables/containers/etc.

[0] https://tools.taskcluster.net/groups/BQGLfmGpS0yxqORLxV8BZw/tasks/IkMc0fFpRJ2bXNw4g0EnNg/runs/0/logs/public%2Flogs%2Flive.log

One thing we discussed was naming the test containers with some regexp-able timestamp, then having a cron hook or the like that can delete very old containers (and tables, etc.).

This might not be worth too much work if postgres is just around the corner..

Component: Platform and Services → Services

Even though this is containers instead of tables, the fix will be the same I think?

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.