Test server seems to not enable time skipping in this specific scenario

Expected Behavior

W2 7 day timer should be unblocked immediately.

Actual Behavior

Timer is not unblocked.

Steps to Reproduce the Problem

(I have not run this myself and verified, this is pseudo code I got from a user on slack)

async function W1() {
    await A1();
    ...
}

async function A1() {
  const ids = runDBQuery();

  const { workflowClient } = getContext();

  await Promise.all(
    ids.map((id) =>
      workflowClient.signalWithStart(W2, {
        taskQueue: "default",
        workflowId: `W2-${id}`,
        args: [
          {
            ...
          },
        ],
        signal: S1,
        signalArgs: [{ ... }],
      })
    ),
  );
}

async function W2() {
    await sleep("7 days");
    await A2();
    ...
}

async function A2() {
    // produce side effect
}

describe("test T1", () => {
    it("alls A2", async () => {
        const testActivities = {
          ...activities,
          A2: jest.fn(),
        };


        const testEnv = await TestWorkflowEnvironment.createTimeSkipping();
        const worker = await Worker.create({
          connection: testEnv.nativeConnection,
          workflowsPath: require.resolve("./allWorkflows"),
          interceptors: appendDefaultInterceptors(
            {
              activityInbound: [
                (ctx) =>
                  new CustomActivityInboundInterceptor(ctx, {
                    workflowClient: testEnv.client.workflow,
                  }),
              ],
            },
            console
          ),
          activities: testActivities,
          taskQueue: "default",
        });

        await worker.runUntil(() => 
          testEnv.client.workflow.execute(
            W1,
            {
              workflowId: randomUUID(),
              taskQueue: "default",
              args: [
                {
                  ...
                },
              ],
            }
          )
        )

        const handle = testEnv.client.workflow.getHandle(`W2-id1`);
        await handle.result();

        expect(testActivities.A2).toHaveBeenCalled();
    })
})

[Spikhalskiy]

@maxgurewitz Thanks for the clarification, it makes more sense if they wait only for a start. I will try to repro it and get back to you, I don’t expect it to be a Test Server bug, but it may be a TS SDK bug. How many workflows does A1 start in your test? One or several?

[bergundy]

Looks like the worker in this example is shut down before the second workflow gets a chance to complete.