Fix Flaky Workflow Test Failure

[cicoyle]

wfCIOutput.txt
link to CI

expected:

Expected stdout (output_match_mode: substring, match_order: none):
		Starting Workflow: io.dapr.examples.workflows.chain.DemoChainWorkflow
		Starting Activity: io.dapr.examples.workflows.chain.ToUpperCaseActivity
		Message Received from input: Tokyo
		Sending message to output: TOKYO
		Starting Activity: io.dapr.examples.workflows.chain.ToUpperCaseActivity
		Message Received from input: London
		Sending message to output: LONDON
		Starting Activity: io.dapr.examples.workflows.chain.ToUpperCaseActivity
		Message Received from input: Seattle
		Sending message to output: SEATTLE
		Workflow finished with result: TOKYO, LONDON, SEATTLE

actual:

time="2025-03-17T10:43:30.017972582Z" level=warning msg="Redis does not support transaction rollbacks and should not be used in production as an actor state store." app_id=demoworkflowworker component="statestore (state.redis/v1)" instance=fv-az1720-24 scope=dapr.contrib type=log ver=1.15.3
		time="2025-03-17T10:43:30.02122285Z" level=info msg="1197ddc2-5b18-4dce-92b0-1bd54f84df1f: starting new 'io.dapr.examples.workflows.chain.DemoChainWorkflow' instance with ID = '1197ddc2-5b18-4dce-92b0-1bd54f84df1f'." app_id=demoworkflowworker instance=fv-az1720-24 scope=dapr.wfengine.durabletask.backend type=log ver=1.15.3
		== APP == 2025-03-17 10:43:30,070 {HH:mm:ss.SSS} [main] INFO  io.dapr.workflows.WorkflowContext - Starting Workflow: io.dapr.examples.workflows.chain.DemoChainWorkflow
		== APP == 2025-03-17 10:43:30,105 {HH:mm:ss.SSS} [main] INFO  i.d.e.w.chain.ToUpperCaseActivity - Starting Activity: io.dapr.examples.workflows.chain.ToUpperCaseActivity
		== APP == 2025-03-17 10:43:30,110 {HH:mm:ss.SSS} [main] INFO  i.d.e.w.chain.ToUpperCaseActivity - Message Received from input: Tokyo
		== APP == 2025-03-17 10:43:30,110 {HH:mm:ss.SSS} [main] INFO  i.d.e.w.chain.ToUpperCaseActivity - Sending message to output: TOKYO
		== APP == 2025-03-17 10:43:30,139 {HH:mm:ss.SSS} [main] INFO  i.d.e.w.chain.ToUpperCaseActivity - Starting Activity: io.dapr.examples.workflows.chain.ToUpperCaseActivity
		== APP == 2025-03-17 10:43:30,139 {HH:mm:ss.SSS} [main] INFO  i.d.e.w.chain.ToUpperCaseActivity - Message Received from input: London
		== APP == 2025-03-17 10:43:30,139 {HH:mm:ss.SSS} [main] INFO  i.d.e.w.chain.ToUpperCaseActivity - Sending message to output: LONDON
		== APP == 2025-03-17 10:43:30,148 {HH:mm:ss.SSS} [main] INFO  i.d.e.w.chain.ToUpperCaseActivity - Starting Activity: io.dapr.examples.workflows.chain.ToUpperCaseActivity
		== APP == 2025-03-17 10:43:30,149 {HH:mm:ss.SSS} [main] INFO  i.d.e.w.chain.ToUpperCaseActivity - Message Received from input: Seattle
		== APP == 2025-03-17 10:43:30,149 {HH:mm:ss.SSS} [main] INFO  i.d.e.w.chain.ToUpperCaseActivity - Sending message to output: SEATTLE
		== APP == 2025-03-17 10:43:30,155 {HH:mm:ss.SSS} [main] INFO  io.dapr.workflows.WorkflowContext - Workflow finished with result: TOKYO, LONDON, SEATTLE

[salaboy]

@mcruzdev this one would be highly appreciated if you take a look at.

[mcruzdev]

@salaboy could you assign it to me, I am investigating...

[salaboy]

Done

[eddumelendez]

I've been reviewing this as well. I can not find an explanation for the error because producer and consumer have the same configuration and producer executes first without error. When consumer executes, the network must be already there.

Currently, GH runner uses Docker 26.1.3, but the last stable version is 28.0.2. WDYT about using Docker GHA and set the socket into the maven command. If you agree, I can open a PR.

[mcruzdev]

I think that this error can be on mechanical-markdown side, before this error we have this one https://github.com/mcruzdev/java-sdk/actions/runs/14039496373/job/39305789353?pr=1 and the stdout contains the expected line.

[salaboy]

@eddumelendez I've sent a PR already

[mcruzdev]

Yes, It is happening on mechanical-markdown side:

Given an step:

name: Run Chaining Pattern workflow
match_order: none
output_match_mode: substring
expected_stdout_lines:
  - 'Activity returned: 2'
  - 'Activity returned: 9'
  - 'Activity returned: 21'
  - 'Activity returned: 17'
  - 'Workflow finished with result: 60'

The verification executes in the expected_stdout_lines in order, then the first line to be verified is Activity returned: 2.

If the output shows first Activity returned: 21 the first line (Activity returned: 2) will be matched and the following line will remove Activity returned: 21 from output.

cc: @salaboy @cicoyle @wcs1only

[mcruzdev]

For this issue the behavior can be a bit different... I am not sure yet. The link to CI provided by @cicoyle points to the error above.

[mcruzdev]

Issue opened!