[Bug]: Test skip ("did not run") without any reason

[tranvannhatnam97]

Version

1.45.3

Steps to reproduce

I run playwright test on bitbucket pipeline.
And here is one of those test:

test("Add curbside special hours", async ({ loginPage }) => {
        test.slow();
        const homePage = new HomePage(loginPage.getPage(), {
            role: Role.ADMIN,
            profile: Profile.PROFILE3,
            hasCanfleet: false,
        });
        await homePage.checkIn();
        await homePage.goToSettings();
        const settingLocationsPage = new SettingLocationsPage(
            homePage.getPage(),
            {
                profile: Profile.PROFILE3,
            }
        );
        await settingLocationsPage.switchToLocations();
        await settingLocationsPage.checkIn();
        const chosenLocation = "4601 Canada Way (SB2) UPDATED 0619";
        await settingLocationsPage.goToEditLocationHasName(chosenLocation);
        const locationEditingPage = new LocationEditingPage(
            settingLocationsPage.getPage()
        );
        await locationEditingPage.checkIn();
        await locationEditingPage.goToFullfillmentSettings("Curbside");
        const locationFullfillmentSettingsPage =
            new LocationFullfillmentSettingsPage(locationEditingPage.getPage());
        await locationFullfillmentSettingsPage.checkIn();
        await locationFullfillmentSettingsPage.addValidSampleSpecialHours();
        await sleep(5000);
    });

Expected behavior

I only set skip for 3 of those tests, so it's expected to only return 3 skipped tests

Actual behavior

Some how it return this

Here is the report

Additional context

My test runs on local runner of bitbucket, using Mac mini device and latest docker image version.
I ran locally and I can assure that there is no over timeout.
Can you explain why? Does it have anything to do with server performance?

Environment

Image: mcr.microsoft.com/playwright:v1.49.0-jammy
Device: MacMini Intel
Local bitbucket-server: https://support.atlassian.com/bitbucket-cloud/docs/runners/

[dgozman]

@tranvannhatnam97 4 did not run means these tests were not even started. That usually happens because:

• testing finished earlier due to a global timeout;
• testing finished earlier due to some other problem in the worker or global setup/teardown;
• testing finished earlier due to maxFailures setting;
• some tests in a serial mode were skipped because of the earlier failers.

Are you using a serial mode, for example test.describe.serial(), by any chance?