trTryGhost
GitHubGhostWorkspace
GitHub
  • CI Pipeline Executions
    • Current executionSucceeded
      claude/e2e-test-failure-check-17f6d9
    • Runs and Agents
    • Configuration
    • Self-Healing CI
    • Project Graph
    • Circular DependenciesEnterprise
    • Resource Usage
    • Analysis
    • ConformanceEnterprise
  • Runs
    • Current runSucceeded
    • Tasks
    • Resource Usage
Insights
  • Compare tasks
  • Analytics
    Fixed a flaky members import E2E test opening a member detail no ref The members list writes its own query string back after something changes it — closing the import modal applies the import's label filter — and that write is a navigation of its own. One landing right after a member row is clicked replaces the detail route with the list again: the detail chunk loads, the member is never fetched, and the assertion waits out its timeout on the list. `import-custom-fields.test.ts` hit this on roughly a quarter of attempts and lost all three retries on 0b8af54, taking the E2E shard red. Re-click the row when the detail screen does not appear, rather than waiting out a timeout on a screen the app navigated away from. The app-side race is real and stays open: a member opened straight after an import can send the reader back to the list. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
    nx run-many -t lint -p @tryghost/e2e
Succeeded
Linux
4 CPU cores
read-write access token used
e76e163930429

See resource usage for your runs

Add the resource usage add-on to record CPU and memory per task on your run's main agent and trace slow runs or out-of-memory failures to the task that caused them.

Add resource usage

© 2026 - Nx Cloud

Terms of ServicePrivacy PolicyChangelogStatusDocsContact Nx CloudPricingCompany@NxDevTools
GitHubGhostWorkspace