Skip to content

feat: Clarify upload queueing logging and process completion logging#110

Open
calvin-codecov wants to merge 3 commits intomainfrom
cy/clarify_report_queue_messaging
Open

feat: Clarify upload queueing logging and process completion logging#110
calvin-codecov wants to merge 3 commits intomainfrom
cy/clarify_report_queue_messaging

Conversation

@calvin-codecov
Copy link
Contributor

@calvin-codecov calvin-codecov commented Mar 17, 2026

Closes #74

The language was confusing for users so I:

  • modified the "Upload" process wording
  • removed the word "Process" that came before the process description for all of the processes as it seemed a bit redundant

For reference, the existing options we have for process_desc are
"Upload" -> "Upload queued for processing"
"Empty Upload"
"Commit creating"
"Base picking"
"Report creating"
"Report results creating"
"Getting report results"
"Upload Completion"
"Posting test results comment".

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

@calvin-codecov calvin-codecov force-pushed the cy/clarify_report_queue_messaging branch from 31f1161 to 9e98e76 Compare March 19, 2026 00:00
@calvin-codecov calvin-codecov marked this pull request as ready for review March 19, 2026 04:48
):
logger.info(
f"Process {process_desc} complete",
f"{process_desc} complete",
Copy link
Contributor Author

Choose a reason for hiding this comment

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

The word "Process" seemed a little redundant to me.

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.

Unclear messaging about report queueing vs processing

2 participants