Review Request 108689: Make KJob realize that there is an error.

[Commit Hook]

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/108689/#review26476
-----------------------------------------------------------


This review has been submitted with commit c96be5e2c114bc1561cd05d1343e80eaf1552aa9 by eli mackenzie to branch 1.5.

- Commit Hook


On Jan. 31, 2013, 8:01 p.m., Eli MacKenzie wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> http://git.reviewboard.kde.org/r/108689/
> -----------------------------------------------------------
> 
> (Updated Jan. 31, 2013, 8:01 p.m.)
> 
> 
> Review request for KDevelop.
> 
> 
> Description
> -------
> 
> Merely setting the error number and error text isn't enough to cause KJob to detect the state of the job, emitResult must be called as well. Otherwise, the job not starting is never detected. I've added a change to set the VcsJob::status as well, might as well be thorough about marking the job as a failure.
> 
> 
> Diffs
> -----
> 
>   vcs/dvcs/dvcsjob.cpp 07f2e033ac05303518baf15ae7659704ada12e5b 
> 
> Diff: http://git.reviewboard.kde.org/r/108689/diff/
> 
> 
> Testing
> -------
> 
> I discovered this while trying to understand why KDevelop froze when trying to open the revision graph. This fixes the freeze, the cause of the revision graph not opening is a separate review.
> 
> 
> Thanks,
> 
> Eli MacKenzie
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20130131/73856014/attachment.html>