opensource/mattermost
3
0
Fork 0
mirror of https://github.com/mattermost/mattermost.git synced 2026-09-24 16:05:00 +08:00
Code Issues Packages Projects Releases Wiki Activity

Raise shard-split HEAVY_MS above sqlstore timing (#36233)

Browse Source 
Made-with: Cursor
This commit is contained in:
Ben Schumacher
2026-04-23 15:24:51 +02:00
committed by GitHub
parent ee9938fead
commit 795672f077
1 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
server/scripts/shard-split.js
+6 -5
View File
@@ -38,11 +38,12 @@ const { execSync } = require("node:child_process");
const SHARD_INDEX = parseInt(process.env.SHARD_INDEX);
const SHARD_TOTAL = parseInt(process.env.SHARD_TOTAL);
const HEAVY_MS = 300000; // 5 min: packages above this get test-level splitting
// Only api4 (~38 min) and app (~15 min) exceed this threshold.
// Packages like sqlstore (~3 min) stay whole to preserve test isolation —
// their integrity tests scan the entire database and break if split across
// shards where other tests leave data behind.
// Threshold for test-level splitting (aggregated pass time from timing cache).
// Keep this above sqlstore: its total time can exceed 5 minutes while remaining
// far below api4/app, and treating sqlstore as "heavy" breaks CI — discovery
// runs `go test -list` on the GitHub host where TestMain cannot reach postgres
// on the docker compose network (only api4 and app should need -list splitting).
const HEAVY_MS = 400000; // 400s (~6.7 min): packages above this get test-level splitting
if (isNaN(SHARD_INDEX) || isNaN(SHARD_TOTAL) || SHARD_TOTAL < 1) {
console.error("ERROR: SHARD_INDEX and SHARD_TOTAL must be set");