Do not lower the seeded pond quota in the comments pack (#92)
Some checks failed
CD / Build and push images (push) Successful in 1m6s
CD / Deploy to Test (push) Successful in 9s
CD / Smoke tests against Test (push) Successful in 1m9s
CD / Promote to Int (push) Successful in 10s
CI / Lint, typecheck, test (push) Successful in 3m19s
CI / Build container images (push) Has been skipped
CI / Auth e2e pack (push) Failing after 2m44s
CI / Import/export fidelity gate (push) Has been skipped
Some checks failed
CD / Build and push images (push) Successful in 1m6s
CD / Deploy to Test (push) Successful in 9s
CD / Smoke tests against Test (push) Successful in 1m9s
CD / Promote to Int (push) Successful in 10s
CI / Lint, typecheck, test (push) Successful in 3m19s
CI / Build container images (push) Has been skipped
CI / Auth e2e pack (push) Failing after 2m44s
CI / Import/export fidelity gate (push) Has been skipped
The seed already grants fixture users additional_ponds headroom (100); overriding it down to 10 made pond creation fail in CI, where the earlier packs' ponds count against the limit. The pack now relies on the seeded override and reports the create-pond response on failure. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EwZ4jR4KFAPvpjWevfUGX1
This commit is contained in:
parent
c7d3b20ca0
commit
c8afe7c8d6
@ -58,11 +58,6 @@ test.afterAll(async ({ browser }) => {
|
||||
const owner = await contextForUser(browser, BASE_URL, 'fixture-user');
|
||||
if (pondId) await owner.request.delete(`/api/v1/ponds/${pondId}`);
|
||||
await owner.close();
|
||||
const admin = await contextForUser(browser, BASE_URL, 'fixture-admin');
|
||||
if (ownerId) {
|
||||
await admin.request.delete(`/api/v1/admin/quotas/user/${ownerId}/additional_ponds`);
|
||||
}
|
||||
await admin.close();
|
||||
});
|
||||
|
||||
test('two users run the full comment lifecycle with resolve/unresolve', async ({ browser }) => {
|
||||
|
||||
Loading…
Reference in New Issue
Block a user