Skip to content

Conversation

@majiru
Copy link
Contributor

@majiru majiru commented Jan 15, 2026

What changed?

Reduce the number of tasks to reduce load in CI to hopefully avoid the context timeout.

Why?

We've observed some flakes in CI for this, this should help.

How did you test it?

  • built
  • run locally and tested manually
  • covered by existing tests
  • added new unit test(s)
  • added new functional test(s)

@majiru majiru requested review from a team as code owners January 15, 2026 07:17
@majiru majiru force-pushed the fairness-flaky-tests branch from db09fb1 to 16c7e20 Compare January 17, 2026 00:02
@majiru majiru force-pushed the fairness-flaky-tests branch from 16c7e20 to 27abd70 Compare January 17, 2026 00:03
@majiru majiru changed the title Wait for workflows and activities to be enqueued in fairness functional test Reduce load on fairness activity functional test Jan 17, 2026
Copy link
Contributor

@dnr dnr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is priority functional test, not fairness? (pr title)


s.OverrideDynamicConfig(dynamicconfig.MatchingNumTaskqueueReadPartitions, 1)
s.OverrideDynamicConfig(dynamicconfig.MatchingNumTaskqueueWritePartitions, 1)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we also wait for the activity tasks to appear in the backlog, to avoid inadvertent sync match that will mess up the order? I guess it's extremely unlikely to mess it up enough to fail the test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants