2) [chromium] › e2e/dashboard-widgets.spec.js:186:5 › contribution graph range buttons request a new range Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(locator).toBeVisible() failed Locator: getByRole('heading', { name: /dashboard/i }) Expected: visible Timeout: 30000ms Error: element(s) not found Call log: - Expect "toBeVisible" with timeout 30000ms - waiting for getByRole('heading', { name: /dashboard/i }) 193 | 194 | await page.goto("/dashboard", { waitUntil: "load" }); > 195 | await expect(page.getByRole("heading", { name: /dashboard/i })).toBeVisible({ timeout: 30000 }); | ^ 196 | await page.getByRole("button", { name: "Show 90-day range" }).first().click(); 197 | await page 198 | .locator("#contribution-activity") at /home/runner/work/devtrack/devtrack/e2e/dashboard-widgets.spec.js:195:67

2) [chromium] › e2e/dashboard-widgets.spec.js:186:5 › contribution graph range buttons request a new range Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Test timeout of 30000ms exceeded.

2) [chromium] › e2e/dashboard-widgets.spec.js:186:5 › contribution graph range buttons request a new range Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(locator).toBeVisible() failed Locator: getByRole('heading', { name: /dashboard/i }) Expected: visible Timeout: 30000ms Error: element(s) not found Call log: - Expect "toBeVisible" with timeout 30000ms - waiting for getByRole('heading', { name: /dashboard/i }) 193 | 194 | await page.goto("/dashboard", { waitUntil: "load" }); > 195 | await expect(page.getByRole("heading", { name: /dashboard/i })).toBeVisible({ timeout: 30000 }); | ^ 196 | await page.getByRole("button", { name: "Show 90-day range" }).first().click(); 197 | await page 198 | .locator("#contribution-activity") at /home/runner/work/devtrack/devtrack/e2e/dashboard-widgets.spec.js:195:67

2) [chromium] › e2e/dashboard-widgets.spec.js:186:5 › contribution graph range buttons request a new range Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Test timeout of 30000ms exceeded.

2) [chromium] › e2e/dashboard-widgets.spec.js:186:5 › contribution graph range buttons request a new range Error: expect(locator).toBeVisible() failed Locator: getByRole('heading', { name: /dashboard/i }) Expected: visible Timeout: 30000ms Error: element(s) not found Call log: - Expect "toBeVisible" with timeout 30000ms - waiting for getByRole('heading', { name: /dashboard/i }) 193 | 194 | await page.goto("/dashboard", { waitUntil: "load" }); > 195 | await expect(page.getByRole("heading", { name: /dashboard/i })).toBeVisible({ timeout: 30000 }); | ^ 196 | await page.getByRole("button", { name: "Show 90-day range" }).first().click(); 197 | await page 198 | .locator("#contribution-activity") at /home/runner/work/devtrack/devtrack/e2e/dashboard-widgets.spec.js:195:67

1) [chromium] › e2e/dashboard-widgets.spec.js:177:5 › dashboard widgets render with mocked metrics Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(locator).toBeVisible() failed Locator: getByRole('heading', { name: /dashboard/i }) Expected: visible Timeout: 30000ms Error: element(s) not found Call log: - Expect "toBeVisible" with timeout 30000ms - waiting for getByRole('heading', { name: /dashboard/i }) 177 | test("dashboard widgets render with mocked metrics", async ({ page }) => { 178 | await page.goto("/dashboard", { waitUntil: "load" }); > 179 | await expect(page.getByRole("heading", { name: /dashboard/i })).toBeVisible({ timeout: 30000 }); | ^ 180 | await expect(page.getByRole("heading", { name: "Your Commits" })).toBeVisible({ timeout: 10000 }); 181 | await expect(page.getByRole("heading", { name: "PR Analytics" })).toBeVisible({ timeout: 10000 }); 182 | await expect(page.getByRole("heading", { name: "Goals", exact: true })).toBeVisible({ timeout: 10000 }); at /home/runner/work/devtrack/devtrack/e2e/dashboard-widgets.spec.js:179:67

1) [chromium] › e2e/dashboard-widgets.spec.js:177:5 › dashboard widgets render with mocked metrics Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Test timeout of 30000ms exceeded.

1) [chromium] › e2e/dashboard-widgets.spec.js:177:5 › dashboard widgets render with mocked metrics Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(locator).toBeVisible() failed Locator: getByRole('heading', { name: /dashboard/i }) Expected: visible Timeout: 30000ms Error: element(s) not found Call log: - Expect "toBeVisible" with timeout 30000ms - waiting for getByRole('heading', { name: /dashboard/i }) 177 | test("dashboard widgets render with mocked metrics", async ({ page }) => { 178 | await page.goto("/dashboard", { waitUntil: "load" }); > 179 | await expect(page.getByRole("heading", { name: /dashboard/i })).toBeVisible({ timeout: 30000 }); | ^ 180 | await expect(page.getByRole("heading", { name: "Your Commits" })).toBeVisible({ timeout: 10000 }); 181 | await expect(page.getByRole("heading", { name: "PR Analytics" })).toBeVisible({ timeout: 10000 }); 182 | await expect(page.getByRole("heading", { name: "Goals", exact: true })).toBeVisible({ timeout: 10000 }); at /home/runner/work/devtrack/devtrack/e2e/dashboard-widgets.spec.js:179:67

1) [chromium] › e2e/dashboard-widgets.spec.js:177:5 › dashboard widgets render with mocked metrics Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Test timeout of 30000ms exceeded.

1) [chromium] › e2e/dashboard-widgets.spec.js:177:5 › dashboard widgets render with mocked metrics Error: expect(locator).toBeVisible() failed Locator: getByRole('heading', { name: /dashboard/i }) Expected: visible Timeout: 30000ms Error: element(s) not found Call log: - Expect "toBeVisible" with timeout 30000ms - waiting for getByRole('heading', { name: /dashboard/i }) 177 | test("dashboard widgets render with mocked metrics", async ({ page }) => { 178 | await page.goto("/dashboard", { waitUntil: "load" }); > 179 | await expect(page.getByRole("heading", { name: /dashboard/i })).toBeVisible({ timeout: 30000 }); | ^ 180 | await expect(page.getByRole("heading", { name: "Your Commits" })).toBeVisible({ timeout: 10000 }); 181 | await expect(page.getByRole("heading", { name: "PR Analytics" })).toBeVisible({ timeout: 10000 }); 182 | await expect(page.getByRole("heading", { name: "Goals", exact: true })).toBeVisible({ timeout: 10000 }); at /home/runner/work/devtrack/devtrack/e2e/dashboard-widgets.spec.js:179:67

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/