Re: Re[2]: Re[2]: Re[2]: Coverity scan results

2016-02-25 Thread Jaroslaw Staniek
On 26 February 2016 at 00:20, Nick Shaforostoff wrote: > >> but if you upload to KDE account, then please build all other kde stuff > >> (it takes 15 hours on my laptop with ssd), otherwise all found issues > for other projects will disappear > > > > > > ​I see, thanks.​ > > > i'll reupload last

Re[2]: Re[2]: Re[2]: Coverity scan results

2016-02-25 Thread Nick Shaforostoff
>> but if you upload to KDE account, then please build all other kde stuff >> (it takes 15 hours on my laptop with ssd), otherwise all found issues for >> other projects will disappear > > > ​I see, thanks.​ > i'll reupload last kde build results which is 7gb compressed tomorrow, please do not

Re: Re[2]: Re[2]: Coverity scan results

2016-02-25 Thread Jaroslaw Staniek
On 25 February 2016 at 17:31, Nick Shaforostoff wrote: > > ​Nick, that's perfect, thanks. I'll try to re-upload my earlier kdb.git > and kexi.git stuff. I believe the red errors I reported earlier may be not > technical but because of permissions. Let's see. > > but if you upload to KDE account,

Re[2]: Re[2]: Coverity scan results

2016-02-25 Thread Nick Shaforostoff
> ​Nick, that's perfect, thanks. I'll try to re-upload my earlier kdb.git and > kexi.git stuff. I believe the red errors I reported earlier may be not > technical but because of permissions. Let's see. but if you upload to KDE account, then please build all other kde stuff (it takes 15 hours on

Re: Re[2]: Coverity scan results

2016-02-25 Thread Jaroslaw Staniek
On 25 February 2016 at 15:48, Nick Shaforostoff wrote: > > > > --- Исходное сообщение --- > От кого: "Jaroslaw Staniek" > Дата: 25 февраля 2016, 15:01:25 > > > > > > > > > Hi Nick, > > BTW, can I become owner of some 'issues' so e.g. I can remove false > positives? > > Doesn't COverity allow

Re[2]: Coverity scan results

2016-02-25 Thread Nick Shaforostoff
--- Исходное сообщение --- От кого: "Jaroslaw Staniek" Дата: 25 февраля 2016, 15:01:25 > > > Hi Nick, > BTW, can I become owner of some 'issues' so e.g. I can remove false positives? Doesn't COverity allow to change issues' properties for 'member/contributors'? anyways, i have chang

Re: Coverity scan results

2016-02-25 Thread Jaroslaw Staniek
Hi Nick, BTW, can I become owner of some 'issues' so e.g. I can remove false positives? On 16 February 2016 at 20:00, Nick Shaforostoff wrote: > Hi! I just wanted to let you know that Coverity static analyzer scan > results are ready for most of KDE packages including Calligra. > > Please look a

Re: Coverity scan results

2016-02-21 Thread Jaroslaw Staniek
My issue stays with a normal email-based login. On 21 February 2016 at 14:29, Tomas Mecir wrote: > Yeah, getting the same problem here (using the github-integration > login, maybe that's the issue). > > 2016-02-20 18:16 GMT+01:00 Pierre : > > On Friday, February 19, 2016 02:05:04 AM Nick Shaforo

Re: Coverity scan results

2016-02-21 Thread Tomas Mecir
Yeah, getting the same problem here (using the github-integration login, maybe that's the issue). 2016-02-20 18:16 GMT+01:00 Pierre : > On Friday, February 19, 2016 02:05:04 AM Nick Shaforostoff wrote: >> > https://scan.coverity.com/projects/kde/view_defects and I then get the >> > message «Failed

Re: Coverity scan results

2016-02-20 Thread Pierre
On Friday, February 19, 2016 02:05:04 AM Nick Shaforostoff wrote: > > https://scan.coverity.com/projects/kde/view_defects and I then get the > > message «Failed to view defects: It may take a few minutes before you can > > view your defects for the first time or when you change your email.» > > wh

Re: Re[2]: Coverity scan results

2016-02-19 Thread Jaroslaw Staniek
It's firefox, and even for 'kde' no defects are displayed. It worked 3 days ago or so. On 19 February 2016 at 01:05, Nick Shaforostoff wrote: > > > https://scan.coverity.com/projects/kde/view_defects and I then get the > message > > «Failed to view defects: It may take a few minutes before you c

Re: Re[2]: Coverity scan results

2016-02-19 Thread Jaroslaw Staniek
It works again, but jsut for 'kde', for kexi ([1] that I created recently for testing extra branches more frequently) it still spits the "Failed to view defects". The support does not respond. [1] https://scan.coverity.com/projects/kexi/view_defects On 19 February 2016 at 01:05, Nick Shaforostof

Re[2]: Coverity scan results

2016-02-18 Thread Nick Shaforostoff
> https://scan.coverity.com/projects/kde/view_defects and I then get the message > «Failed to view defects: It may take a few minutes before you can view your > defects for the first time or when you change your email.» which browser do you use? i use chromium and it works fine. if the problem pe

Re: Coverity scan results

2016-02-18 Thread Jaroslaw Staniek
On 18 February 2016 at 19:24, Pierre wrote: > On Tuesday, February 16, 2016 09:00:58 PM Nick Shaforostoff wrote: > > Hi! I just wanted to let you know that Coverity static analyzer scan > results > > are ready for most of KDE packages including Calligra. > > > > Please look at the results via > >

Re: Coverity scan results

2016-02-18 Thread Pierre
On Tuesday, February 16, 2016 09:00:58 PM Nick Shaforostoff wrote: > Hi! I just wanted to let you know that Coverity static analyzer scan results > are ready for most of KDE packages including Calligra. > > Please look at the results via > https://scan.coverity.com/projects/kde?tab=overview Hi I

Re: Re[2]: Coverity scan results

2016-02-16 Thread Jaroslaw Staniek
On 16 February 2016 at 22:44, Jaroslaw Staniek wrote: > > > On 16 February 2016 at 21:58, Nick Shaforostoff wrote: > >> > Is this for calligra.git master? >> calligra master as of January 29th - i had troubles uploading such a >> large build data (6.5GB xz-compressed) >> >> ​I still see calligra

Re: Re[2]: Coverity scan results

2016-02-16 Thread Jaroslaw Staniek
On 16 February 2016 at 21:58, Nick Shaforostoff wrote: > > Is this for calligra.git master? > calligra master as of January 29th - i had troubles uploading such a large > build data (6.5GB xz-compressed) > > > Do you think it would be possible to also have other active Calligra > code covered? >

Re[2]: Coverity scan results

2016-02-16 Thread Nick Shaforostoff
> Is this for calligra.git master? calligra master as of January 29th - i had troubles uploading such a large build data (6.5GB xz-compressed) > Do you think it would be possible to also have other active Calligra code > covered? > > - master for kexi.git > - master for kdiagram.git > - master

Re: Coverity scan results

2016-02-16 Thread Jaroslaw Staniek
On 16 February 2016 at 20:00, Nick Shaforostoff wrote: > Hi! I just wanted to let you know that Coverity static analyzer scan > results are ready for most of KDE packages including Calligra. > > Please look at the results via > https://scan.coverity.com/projects/kde?tab=overview > > > ​ Thank you

Coverity scan results

2016-02-16 Thread Nick Shaforostoff
Hi! I just wanted to let you know that Coverity static analyzer scan results are ready for most of KDE packages including Calligra. Please look at the results via https://scan.coverity.com/projects/kde?tab=overview ___ calligra-devel mailing list