Nx
Enterprise
Nx
Overview
Sign in / Sign up
Open main menu
Nx
GitHub
Select a tab
Overview
Runs
Analytics
Nx
GitHub
Overview
Runs
Analytics
Loading workspace stats
Loading workspace insights...
Statistics interval
7 days
30 days
Latest CI Pipeline Executions
Filter range
Sort by
Sort by
Start time
Sort ascending
Sort descending
Filter
Filter exact branch match
Exact
Select status
Failed
32395
3bd19212 fix(core): resolve TypeScript error for cache property in HashedTask - Add cache field to native Task struct to match TypeScript interface - Change HashedTask.cache from optional to required boolean type - Update database schema to make cache column NOT NULL with default - Use null coalescing in hash-task.ts to provide default cache values - Rebuild native module to generate correct TypeScript bindings This resolves the CI error: "Object literal may only specify known properties, and 'cache' does not exist in type 'HashedTask'"
2 months ago
by FrozenPandaz
Failed
32395
256347d0 fix(core): update generated TypeScript bindings for cache property
2 months ago
by FrozenPandaz
Failed
32395
a7cd8ce8 fix(core): update generated TypeScript bindings for cache property
2 months ago
by FrozenPandaz
Canceled
32395
60d047b3 fix(core): resolve TypeScript error for cache property in HashedTask - Add cache field to native Task struct to match TypeScript interface - Change HashedTask.cache from optional to required boolean type - Update database schema to make cache column NOT NULL with default - Use null coalescing in hash-task.ts to provide default cache values - Rebuild native module to generate correct TypeScript bindings This resolves the CI error: "Object literal may only specify known properties, and 'cache' does not exist in type 'HashedTask'"
2 months ago
by FrozenPandaz
Failed
32395
f92bd5ea fix(core): exclude non-cacheable tasks from flaky detection Non-cacheable tasks like development servers are expected to have inconsistent results and should not be considered flaky. This change modifies the flaky task detection to only consider explicitly cacheable tasks (cache = true) when identifying flaky behavior. - Add cache field to task_details table and HashedTask struct - Update flaky task query to exclude non-cacheable tasks - Pass cache information from TypeScript to native layer - Add comprehensive tests for new behavior 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2 months ago
by FrozenPandaz
Failed
32395
15388578 fix(core): exclude non-cacheable tasks from flaky detection Non-cacheable tasks like development servers are expected to have inconsistent results and should not be considered flaky. This change modifies the flaky task detection to only consider explicitly cacheable tasks (cache = true) when identifying flaky behavior. - Add cache field to task_details table and HashedTask struct - Update flaky task query to exclude non-cacheable tasks - Pass cache information from TypeScript to native layer - Add comprehensive tests for new behavior 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2 months ago
by FrozenPandaz
Failed
32395
3240d423 fix(core): exclude non-cacheable tasks from flaky detection Non-cacheable tasks like development servers are expected to have inconsistent results and should not be considered flaky. This change modifies the flaky task detection to only consider explicitly cacheable tasks (cache = true) when identifying flaky behavior. - Add cache field to task_details table and HashedTask struct - Update flaky task query to exclude non-cacheable tasks - Pass cache information from TypeScript to native layer - Add comprehensive tests for new behavior 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2 months ago
by FrozenPandaz
Failed
32395
37653fb7 fix(core): exclude non-cacheable tasks from flaky detection Non-cacheable tasks like development servers are expected to have inconsistent results and should not be considered flaky. This change modifies the flaky task detection to only consider explicitly cacheable tasks (cache = true) when identifying flaky behavior. - Add cache field to task_details table and HashedTask struct - Update flaky task query to exclude non-cacheable tasks - Pass cache information from TypeScript to native layer - Add comprehensive tests for new behavior 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2 months ago
by FrozenPandaz
Failed
32395
429a6c50 fix(core): exclude non-cacheable tasks from flaky detection Non-cacheable tasks like development servers are expected to have inconsistent results and should not be considered flaky. This change modifies the flaky task detection to only consider explicitly cacheable tasks (cache = true) when identifying flaky behavior. - Add cache field to task_details table and HashedTask struct - Update flaky task query to exclude non-cacheable tasks - Pass cache information from TypeScript to native layer - Add comprehensive tests for new behavior 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2 months ago
by FrozenPandaz
Previous page
Previous
Next
Next page