setInterval with 0 or negative value has unexpected behavior

Describe the bug

Hello vitest team !

When running tests for a setInterval function with vi fake timers, I ran into some unexpected behavior with 0 or negative value.
Normally the delay is expected to be 1ms if you write a setInterval with 0 or a negative values, but in my case I just got the following behavior:

• with 0: if I call vi.advanceTimersToNextTimer(); or vi.advanceTimersByTime(1); the set Interval just completes right away and runs all of the callbacks until clearInterval() is called, similar tovi.runAllTimers();.
• with negative value: vi.advanceTimersToNextTimer(); works, however vi.advanceTimersByTime(1); does not, so I guess some other value is set as the timer delay.

I had already run some similar tests with setTimeout, and in this case it works perfectly as expected.

Thanks for your help !

Reproduction

This is the test file I used.

import {
  afterEach, beforeEach, describe, expect, it, vi,
} from 'vitest';

describe('set interval', () => {
  beforeEach(() => {
    vi.useFakeTimers();
  });

  afterEach(() => {
    vi.useRealTimers();
  });

  it('should set interval with 0', () => {
    let i = 0;
    const interval = setInterval(() => {
      i += 1;
      if (i === 3) { clearInterval(interval); }
    }, 0);
    expect(i).toBe(0);
    vi.advanceTimersToNextTimer(); // same result with vi.advanceTimersByTime(1);
    expect(i).toBe(1); // AssertionError: expected 3 to be 1 // Object.is equality
  });

  it('should set interval with negative value', () => {
    let i = 0;
    const interval = setInterval(() => {
      i += 1;
      if (i === 3) { clearInterval(interval); }
    }, -300);
    expect(i).toBe(0);
    vi.advanceTimersToNextTimer();
    expect(i).toBe(1); // OK
    vi.advanceTimersByTime(1);
    expect(i).toBe(2); // AssertionError: expected 1 to be 2 // Object.is equality
  });
});

System Info

System:
    OS: Windows 10 10.0.19045
    CPU: (16) x64 11th Gen Intel(R) Core(TM) i7-11850H @ 2.50GHz
    Memory: 6.54 GB / 15.67 GB
  Binaries:
    Node: 19.5.0 - C:\Program Files\nodejs\node.EXE
    npm: 9.3.1 - C:\Program Files\nodejs\npm.CMD
  npmPackages:
    @vitejs/plugin-legacy: ^2.3.1 => 2.3.1
    @vitest/coverage-istanbul: ^0.33.0 => 0.33.0
    vite: ^3.2.5 => 3.2.7
    vitest: ^0.33.0 => 0.33.0

Used Package Manager

npm

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

Start with the supplied TypeScript reproduction and run it with vi.useFakeTimers(), comparing setInterval behavior for 0 and -300 with the setTimeout case. Trace the fake-timer interval scheduling and add regression coverage so advancing by the next timer or by 1ms produces one callback before clearInterval().