diff --git a/docs/RELIABILITY-1.25.2.md b/docs/RELIABILITY-1.25.2.md index 4a1eec41..3e8a7457 100644 --- a/docs/RELIABILITY-1.25.2.md +++ b/docs/RELIABILITY-1.25.2.md @@ -71,3 +71,13 @@ readBudgetPolicyVersion=3把多文件/原工件读取作为共享预算批次, 完整回归首项浏览器失败经独立复验仍失败;对原1.25.1不可变发行也复现了同一失败,不能归因缺少浏览器。真实Edge检查已通过,但旧保守growth=2560令read_browser_result的页面内容仅返回10/1419字符,原HTTP模型夹具因找不到“已完成”返回500。这与真实供应商故障分开,所有请求均为自有HTTP夹具。对照原文及每次输入估算见browser-paging-comparison.json。 v3页预算把纯read_browser_result视为不会创建计划/作业/变更的读取,按512加有界每调用增长预留;v1/v2及其它混合批次原算法不变,完整请求预算仍独立核对。受控假设构建补全宿主配套入口/Playwright后4请求读取完整1419字符,最后实际输入12105≤12352;两次QA缺输入失败日志仍保留,不当产品失败或发行证明。随后从实际修改源码重新独立编译,原浏览器API全4/4与读取9/9通过;增强原HTTP用例,逐次断言16K/2048/1600内、完整原字段、4请求且无夹具重试。证据browser-growth-source.tap及browser-growth-read-related.tap。共用dist尚未重建,等待首轮完整测试结束再统一构建最终候选,避免运行中更换载荷。 + +### 发行门禁复核及确定性TLS测试 + +4a49f02d的不可变候选20261104123124956已完成源码ZIP独立622输入/22编译一致、三归档、便携八套50组及文件9/结果16/读取10组,实际隔离安装12组与安装副本十套75组。完整复验898/899,唯一失败是本地TLS测试:80ms到期时TCP回调尚未调度,实际正确归类tcp而旧断言固定tls。原断言独立11/11通过,说明该短期限与同步进度落盘/调度存在竞争,不能把它写成TLS网络故障。 + +测试保留真实TCP/TLS套接字,等待auto/IPv4两份ClientHello实际到达后再推进原80ms时钟;79ms两路仍running/tls、80ms必须TLS_HANDSHAKE_TIMEOUT,随后恢复真实时钟检查取消和所属套接字关闭。期限与产品默认值未改。首次补强误读start返回的初始快照(0条trial)明确失败,已改读active operation;新专项11/11通过,原日志均保留。 + +便携基础验收前两次受控Harness在15秒内未ready,initialize/模型/工具均0,所属进程树已关闭;第二次ready实际在spawn后16.36秒才出现。它们均与完整测试并行,不能直接认定为偶发并删除。之后逐一排除PATH、目录与安装/插件身份差异:精简PATH及原checkout/temp布局的独立启动均约1.1秒;实际编译宿主的pipe/脱离控制台+文件输出两种完整受控工程验证都通过,四次native启动约0.6秒。完整测试结束后的同候选便携基础验收也在原15秒门槛下通过。证据为startup-*、compiled-startup-*和portable-quiescent.log。已确认并发背景差异,但超时唯一根因及高负载稳定性仍未知,未提高等待或重试真实模型。 + +因测试输入更改,旧候选及全部首失败不覆盖;下一从新提交重封候选,主要验收串行执行。正式仍1.25.1/PID36552,X尚未冻结或发送。 diff --git a/findings.md b/findings.md index bb322ef1..8c63a158 100644 --- a/findings.md +++ b/findings.md @@ -2,6 +2,8 @@ ## 1.25.2 起点 +发行复核:full-final为898/899,唯一TLS短期限断言与同步progress落盘竞争。真实两份ClientHello后控制原80ms时钟,79ms两路仍TLS、80ms超时,再用真实时钟验证取消/关闭,专项11/11。首次补强错读start初始快照失败,已改active operation。两次便携Harness超时均与full并行;相同PATH/原cwd/temp的独立probe约1.1秒,编译pipe/detached两套受控工程全过(四次ready约0.6秒),full结束后原候选完整便携在原15秒内通过。不能由此证明超时唯一根因或高负载稳定,旧失败保持,新候选主要门禁串行。 + 独立复核已离线复现:v2证明自报顺序可排除实际最新高回执;安装full扫描后到inventory之间的可选文件硬链接变化未被拒;W第6轮新读468字符仍因其后三次重复读取停止,shadow却为evidence_growth。119份W清单长度/SHA正确,相关49/49通过,不代表这些边界已覆盖。基线532b9d60干净。原报告在.qa/independent-review-1.25.1/REVIEW.md,原失败不改写。当前用户已授权修复、开发和小步本地提交,包括修复后新冻有界实验;仍不续跑旧样本/提取Key/推送/委派。 当前1.25.0已完整本地交付:主1420份/158277434字节与补充6份/50722字节离线通过,含两份manifest的1428份/158780733字节Git索引原字节一致。首索引被`*.log`漏掉81份原日志而拒绝,只新增本版两处目录例外后通过;首错误保留在docs/task-agreement-1.25-index-first.txt,成功收据见docs/task-agreement-1.25-git-index.txt。最终验收与回顾见docs/QA-TASK-AGREEMENT-1.25.md及docs/RETROSPECTIVE-TASK-AGREEMENT-1.25.md。以下为分阶段发现,旧“等待/尚无”按当时时点理解;真实模型交付、网络恢复、重复读取改善和Purge收益仍未验证。 diff --git a/progress.md b/progress.md index f6bf789c..9ac905b8 100644 --- a/progress.md +++ b/progress.md @@ -2,6 +2,9 @@ ## 1.25.2 可靠性闭环 +- full-final结束898/899,TLS边界用例的原短计时与TCP调度竞争;原断言独立11/11。改为真实ClientHello后推进原80ms时钟,79ms检查两条实际TLS trial、80ms必须超时,取消仍真实I/O,最终11/11。补强初次读初始快照导致0!=2失败保留,已更正。仅测试修正,无产品期限调整。 +- 前两次便携基础验收native启动超时均与完整测试并行,原失败/第二次16.36秒ready保留。精简PATH/原目录独立probe、编译pipe/detached两套完整受控工程及full结束后的同候选完整便携均通过;确认背景差异而不武断指定唯一根因。计划重封新候选、串行主要门禁,正式和真实模型尚未操作。 + - 接续回看源码1440/390预算原图,修正正式驱动两处候选版本并本地提交b4e1569c。实际更新状态Edge/Electron7组通过并回看原图;基础文件首7/9遇到刷新iframe脱离,仅为只读隔离检查加有界重取文档,完整新9/9通过。首失败与复验原目录保留。 - 8套要求/shadow/草案/诊断实际UI共50组全过,source-ui.json绑定结果/日志及客户端原字节。真实模型0。X冻结已改为绑定实际安装候选源码提交,并将验收文档后的HEAD另记reviewedHead(a3210fa5)。 - 首全量浏览器失败独立复验与原1.25.1均复现:纯读取页只返回10/1419字符,非浏览器缺失。v3按实际只读类型预留后,实际修改源码的独立编译原4/4浏览器API及读取9/9通过;完整页1419、最终请求12105≤12352,原断言增强不放宽。首失败、假设构建缺入口/库的两次QA准备失败、完整输入后的假设通过与实际源码通过分列保存;共享dist在首全量完成前保持不变。 diff --git a/tests/network-diagnostics.test.mjs b/tests/network-diagnostics.test.mjs index e7ad3ff5..ca95a034 100644 --- a/tests/network-diagnostics.test.mjs +++ b/tests/network-diagnostics.test.mjs @@ -79,11 +79,27 @@ test('TLS validation succeeds for a trusted owned certificate and rejects the sa assert.notEqual(bad.trials[0].certificateAuthorized, true); }); -test('a TCP peer that never answers TLS is bounded, and cancellation waits for owned sockets to close', async t => { - let open = 0; const f = setup(t, { stageTimeoutMs: 80 }); - const server = net.createServer(socket => { open++; socket.on('data', () => {}); socket.on('close', () => open--); }); +test('a TCP peer that never answers TLS is bounded, and cancellation waits for owned sockets to close', { timeout: 15000 }, async t => { + let open = 0, clientHellos = 0, handshakesStarted; + const handshakes = new Promise(resolve => { handshakesStarted = resolve; }); + const f = setup(t, { stageTimeoutMs: 80 }); + const server = net.createServer(socket => { + open++; socket.once('data', () => { if (++clientHellos === 2) handshakesStarted(); }); socket.on('close', () => open--); + }); const port = await listener(f, server), connection = f.add('https://127.0.0.1:' + port + '/v1'); - const timed = await f.run(connection); assert.equal(timed.trials[0].stage, 'tls'); assert.equal(timed.trials[0].code, 'TLS_HANDSHAKE_TIMEOUT'); + // Keep real TCP/TLS I/O, but advance its deadline only after both local + // ClientHellos arrive. Synchronous progress persistence must not turn a TLS + // timeout assertion into a race with TCP connection scheduling. + t.mock.timers.enable({ apis: ['setTimeout'] }); + const started = f.manager.start({ id: connection.id, revision: connection.revision }); + const operation = f.manager.active.get(started.job.id), completed = operation.promise; + await handshakes; t.mock.timers.tick(79); + assert.equal(operation.job.status, 'running'); + assert.equal(operation.job.trials.filter(row => row.status === 'running').length, 2); + assert.ok(operation.job.trials.filter(row => row.status === 'running').every(row => row.stage === 'tls')); + t.mock.timers.tick(1); await completed; t.mock.timers.reset(); + const timed = f.manager.view().jobs.find(row => row.id === started.job.id); + assert.equal(timed.trials[0].stage, 'tls'); assert.equal(timed.trials[0].code, 'TLS_HANDSHAKE_TIMEOUT'); await until(() => open === 0); f.manager.options.stageTimeoutMs = 10000; const { job } = f.manager.start({ id: connection.id, revision: connection.revision }); await until(() => open > 0); assert.throws(() => f.manager.start({ id: connection.id, revision: connection.revision }), /等待/);