Flaky: soak.spec matches the previous post's status line #256

New issue

Closed

opened 2026-10-21 23:48:23 +00:00 by littlefox · 1 comment

littlefox commented

2026-10-21 23:48:23 +00:00

Owner

CI run #410 (PR #254): soak.spec.ts failed with expect(no).not.toBe(lastNo), "416" twice.

After Skicka, the spec waits for the status to contain "Inlägg N är publicerat" and then reads N. The previous post's status line still says that, so the wait passes at once and N is the old number, before the new status replaces it. The spec's own comment says the previous post's status line mustn't count; the check catches it, but by failing.

Fix: wait until the status has a number other than the last one. A post that was never made still fails, by timing out.

CI run #410 (PR #254): `soak.spec.ts` failed with `expect(no).not.toBe(lastNo)`, "416" twice. After Skicka, the spec waits for the status to contain "Inlägg N är publicerat" and then reads N. The previous post's status line still says that, so the wait passes at once and N is the old number, before the new status replaces it. The spec's own comment says the previous post's status line mustn't count; the check catches it, but by failing. Fix: wait until the status has a number other than the last one. A post that was never made still fails, by timing out.

littlefox added this to the 0.6: Performance milestone

2026-10-21 23:48:23 +00:00

littlefox added the

area/ci

kind/bug

labels

2026-10-21 23:48:23 +00:00

littlefox referenced this issue from a pull request that will close it,

2026-10-22 00:09:46 +00:00

Read by being seen without reloading the thread; redraw only what changed #254

littlefox referenced this issue from a commit

2026-10-22 00:09:48 +00:00