Skip to content
This repository has been archived by the owner on Aug 25, 2023. It is now read-only.

Yacht-1317: Our error reporting system doesn't work #145

Closed
wants to merge 2 commits into from

Conversation

przemyslaw-jasinski
Copy link
Contributor

No description provided.

@coveralls
Copy link

Pull Request Test Coverage Report for Build 1177

  • 14 of 14 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.05%) to 84.344%

Totals Coverage Status
Change from base Build 1174: 0.05%
Covered Lines: 2419
Relevant Lines: 2868

💛 - Coveralls

1 similar comment
@coveralls
Copy link

Pull Request Test Coverage Report for Build 1177

  • 14 of 14 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.05%) to 84.344%

Totals Coverage Status
Change from base Build 1174: 0.05%
Covered Lines: 2419
Relevant Lines: 2868

💛 - Coveralls

try:
self.__process(request_body_json)
self._finish_with_success()
except CopyJobError, e:
Copy link
Contributor

Choose a reason for hiding this comment

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

I used to think that returning 200 here was intended, because afterBackupActionHandler is not responsible for retrying copyJobs etc.
We were calling ErrorReporting to know that backups finished in not expected way. We want to know about that situation.

I case of this errors, we can't do anything with then, even if we retry whole task again.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants