The worker is able to report the progressPercent of a task, as well as the progressMessage, which should both be returned in the GetSessionActions API.
We should confirm that this functionality is working properly, to prevent future regressions.
What was the solution? (How)
Add a test to make sure that the progressPercent and progressMessage fields are reported as expected.
What is the impact of this change?
Better code quality in the future regarding the progressPercent and progressMessage reporting logic in the worker.
How was this change tested?
# Linux
source .e2e_linux_infra.sh
hatch run linux-e2e-test
hatch run cross-os-e2e-test
# Windows
source .e2e_windows_infra.sh
hatch run windows-e2e-test
hatch run cross-os-e2e-test
Was this change documented?
No
Is this a breaking change?
No
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
What was the problem/requirement? (What/Why)
The worker is able to report the progressPercent of a task, as well as the progressMessage, which should both be returned in the
GetSessionActions
API.We should confirm that this functionality is working properly, to prevent future regressions.
What was the solution? (How)
Add a test to make sure that the progressPercent and progressMessage fields are reported as expected.
What is the impact of this change?
Better code quality in the future regarding the
progressPercent
andprogressMessage
reporting logic in the worker.How was this change tested?
Was this change documented?
No
Is this a breaking change?
No
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.