Review Request 116772: Fix dvcs test break

[Shubham Chaudhary]

> On March 13, 2014, 4:17 p.m., Aleix Pol Gonzalez wrote:
> > vcs/dvcs/dvcsjob.cpp, line 242
> > <https://git.reviewboard.kde.org/r/116772/diff/2/?file=253611#file253611line242>
> >
> >     Well, you only emit result if the job has finished.
> >     
> >     It doesn't make much sense doing it right after startOutput()

If we don't send an emitResult in error slot, looks like it is polling and getting timedout: poll([{fd=3, events=POLLIN}, {fd=6, events=POLLIN}], 2, 9990) = 0 (Timeout) for our test case. 


- Shubham


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/116772/#review52880
-----------------------------------------------------------


On March 13, 2014, 4:06 a.m., Shubham Chaudhary wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/116772/
> -----------------------------------------------------------
> 
> (Updated March 13, 2014, 4:06 a.m.)
> 
> 
> Review request for KDevelop.
> 
> 
> Repository: kdevplatform
> 
> 
> Description
> -------
> 
> AFAICS We don't need to call jobIsReady if there is some error, SlotProcessError is supposed do that already. This patch fixes the broken dvcsTest.
> 
> 
> Diffs
> -----
> 
>   vcs/dvcs/dvcsjob.cpp 30a3fcc 
> 
> Diff: https://git.reviewboard.kde.org/r/116772/diff/
> 
> 
> Testing
> -------
> 
> Totals: 3 passed, 0 failed, 0 skipped
> ********* Finished testing of DVcsJobTest *********
> 
> 
> Thanks,
> 
> Shubham Chaudhary
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20140313/60e4a4ae/attachment-0001.html>