Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Parameter to control if report failures should be fatal #25

Open
GoogleCodeExporter opened this issue May 14, 2015 · 3 comments
Open

Parameter to control if report failures should be fatal #25

GoogleCodeExporter opened this issue May 14, 2015 · 3 comments
Labels
auto-migrated enhancement

Comments

@GoogleCodeExporter
Copy link 

Add a parameter to the DefaultLifeCycleManager manager that controls if report 
failures should be fatal (throw an exception) or if they should only be logged. 
See also issue 22.

Original issue reported on code.google.com by richard.eckart on 3 Apr 2013 at 9:36
@GoogleCodeExporter
Copy link
Author

Original comment by richard.eckart on 3 Apr 2013 at 9:59

  • Added labels: Milestone-0.10.0
  • Removed labels: Milestone-0.9.0

@GoogleCodeExporter
Copy link
Author 

Mind that reports are fatal since issue 24 commit 
a72b6eef373cdc5e6726024c01221aac47db6315 
(DefaultLifeCycleManager.complete(TaskContext, Task):96-98) . This issue is 
really just about allowing to configure that reports should be non-fatal.

Original comment by richard.eckart on 19 May 2013 at 12:00

@GoogleCodeExporter
Copy link
Author

Original comment by richard.eckart on 1 Sep 2013 at 10:29

  • Removed labels: Milestone-0.10.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@reckart @GoogleCodeExporter