test(integration): drop tight 30s timeout in sleep-interception e2e (#4878)

The four sleep-interception integration tests hardcoded a 30s per-test
timeout. That is shorter than the test rig's own per-operation timeout in CI
(60s), and each test performs more than one such operation, so under Docker
sandbox load with the CI model the tests intermittently exceed 30s and fail
(most recently 'should allow sleep < 2s' timed out on all retries, failing the
release Docker integration job). Drop the override so they use the suite's
default timeout, consistent with the other integration tests.
This commit is contained in:
tanzhenxin 2026-06-09 11:22:56 +08:00 committed by GitHub
parent 643a7d4198
commit ce074d93f1
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -34,7 +34,7 @@ describe('sleep-interception', () => {
// The model's output should mention it was blocked
expect(result.toLowerCase()).toContain('blocked');
}, 30000);
});
it('should allow sleep < 2s', async () => {
rig = new TestRig();
@ -51,7 +51,7 @@ describe('sleep-interception', () => {
// Should not be blocked — model should complete successfully
expect(result.toLowerCase()).not.toContain('blocked');
}, 30000);
});
it('should allow retrying blocked sleep with an intentional sleep comment', async () => {
rig = new TestRig();
@ -70,7 +70,7 @@ describe('sleep-interception', () => {
expect(foundShell).toBeTruthy();
expect(result.toLowerCase()).toContain('done');
}, 30000);
});
it('should block sleep >= 2s even when followed by a trailing comment', async () => {
// The `trimTrailingShellComment` state machine strips trailing `#...`
@ -93,5 +93,5 @@ describe('sleep-interception', () => {
// Model must report it was blocked despite the trailing comment.
expect(result.toLowerCase()).toContain('blocked');
}, 30000);
});
});