Skip to content

Worker: fix an issue with batch logging#1353

Merged
josephjclark merged 18 commits intorelease/nextfrom
investigate-flaky-tests
Apr 10, 2026
Merged

Worker: fix an issue with batch logging#1353
josephjclark merged 18 commits intorelease/nextfrom
investigate-flaky-tests

Conversation

@josephjclark
Copy link
Copy Markdown
Collaborator

@josephjclark josephjclark commented Apr 2, 2026

Short Description

Fixes #1350

See issue

Implementation Details

Ok so I don't know the exact case that's causing intermittend fails - but what I've done is manually re-write the tests for the event processor in a much more unit testy way. This divorces the event processor from the runtime and lets me have much more control over tests, so I can recreate particular scenarios more reliably.

The more integration style tests, involving the engine, are still useful - so they're in.

AI Usage

Please disclose whether you've used AI anywhere in this PR (it's cool, we just
want to know!):

  • I have used Claude Code
  • I have used another model
  • I have not used AI

You can read more details in our
Responsible AI Policy

@github-project-automation github-project-automation bot moved this to New Issues in Core Apr 2, 2026
@josephjclark
Copy link
Copy Markdown
Collaborator Author

claude may have found a gap which can cause problems - but that fix doesn't help the actual problem

@josephjclark josephjclark force-pushed the investigate-flaky-tests branch from b75de8c to 9b223c2 Compare April 7, 2026 14:42
@josephjclark josephjclark changed the title Investigate flaky tests Worker: fix an issue with batch logging Apr 8, 2026
@josephjclark josephjclark marked this pull request as ready for review April 8, 2026 17:35
@josephjclark
Copy link
Copy Markdown
Collaborator Author

I'll fix the build and typings in the morning 😫

@josephjclark josephjclark changed the base branch from main to release/next April 9, 2026 15:23
@josephjclark josephjclark merged commit 1cd60b8 into release/next Apr 10, 2026
1 check was pending
@josephjclark josephjclark deleted the investigate-flaky-tests branch April 10, 2026 09:09
@github-project-automation github-project-automation bot moved this from New Issues to Done in Core Apr 10, 2026
josephjclark added a commit that referenced this pull request Apr 10, 2026
* update the worker to node 24 (#1357)

* update the worker to node 24

* update docker docs

* changeset

* Worker: fix an issue with batch logging (#1353)

* set min-release-age

* versions

* debugging flaky test

* fix an issue where the batch is never clear

* fix a timing issue when sending batch events

Big help from claude

* logging

* add a bunch of more controlled unit tests

* test on interrupt

* update and fix tests

I think this this fixes the actual issue - I just want more good focused tests now

* tidy logging

* more tests

* changeset

* types

* remove only

* run tests in serial

* worker: tweak event processor and be sure to reset timeout on batch

* remove comment

* remove more comments

* feat: update usage of getActiveProject to getCheckedOutProject (#1360)

* feat: update getActiveProject to getCheckedOutProject

* feat: back to active project

* chore: rename getActiveProject to getTrackedProject

* feat: deploy should use getTrackedProject

* chore: getCheckedout return undefined like getActiveprojects

* fix: types

* feat: update removed & renamed workflows on checkout (#1358)

* tests: remove unwanted fields

* feat: use currentProject

* tests: remove fields

* versions

---------

Co-authored-by: Farhan Y. <yahyafarhan48@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

Flaky integration test: run:complete triggers before step:complete

2 participants