End-to-end tests: push the real histories one at a time again, until side by side is proven stable (#248)
* End-to-end tests: push the real histories one at a time again
- CI / Typecheck and bundlesuccess
- CI / Unit tests (1/2)success
- CI / Unit tests (2/2)success
- Deploy / Deploy to Cloudflaresuccess
- Deploy / Main's current tipsuccess
- End-to-end / End-to-end (agent reviews, tasks, Today)success
- End-to-end / End-to-end (git, PRs, Actions)success
- End-to-end / End-to-end (large pushes)success
- End-to-end / End-to-end (passkeys, registry, email)Failed
- End-to-end / End-to-end (real histories)success
- End-to-end / End-to-end (runner Docker)success
- End-to-end / End-to-end (security)success
- Live test / Containers, registry, sandboxes, webhooks, schedules, LFS and pull requestssuccess
1 file changed+4−4
modifiedapps/diffinery/test/e2e/e2e.test.mjs+4−4View file
| @@ -2873,10 +2873,10 @@ | ||
| 2873 | 2873 | await g(out, ["fsck", "--full"]); |
| 2874 | 2874 | } |
| 2875 | 2875 | |
| 2876 | -// Side by side, each on a server of its own: one big push keeps one server process busy, so on | |
| 2877 | -// separate processes they use the runner's other cores and take about as long as jquery's alone | |
| 2878 | -// instead of the sum. The lockfile's push uses the shared server. | |
| 2879 | -describe("real histories: whole projects, side by side", { concurrency: true }, () => { | |
| 2876 | +// One at a time, each on a server of its own (the lockfile's on the shared one). Side by side they | |
| 2877 | +// overloaded wrangler dev's proxy (a 500 mid-push or mid-clone in about one run in five) until that | |
| 2878 | +// is proven fixed. | |
| 2879 | +describe("real histories: whole projects, one at a time", { concurrency: false }, () => { | |
| 2880 | 2880 | for (const [name, url, sha] of [ |
| 2881 | 2881 | // 37 MB: staged in R2 and unpacked in pieces. |
| 2882 | 2882 | ["jquery", "https://github.com/jquery/jquery", "c2f27864e4ffc2d1409c289fcb9a42b6165dfeaf"], |