> On 28. Jun 2019, at 00:57, Thiago Macieira wrote:
>
> On Thursday, 27 June 2019 08:24:40 PDT Konstantin Tokarev wrote:
>> 27.06.2019, 18:12, "Thiago Macieira" :
>>> On Thursday, 27 June 2019 07:10:36 PDT Frederik Gladhorn wrote:
The only real challenge was upgrading Bazel, since every
> On 05 Dec 2016, at 14:11, Milian Wolff wrote:
Hi Milian,
> I'd like to see that happen, more testing is always a win. But we will need
> to
> learn from the coverity lessons:
which lessons? Feel free to reply off-list.
regards
holger
> On 05 Dec 2016, at 14:11, Milian Wolff wrote:
Hi Milian,
> I'd like to see that happen, more testing is always a win. But we will need
> to
> learn from the coverity lessons:
which lessons? Feel free to reply off-list.
regards
holger
> On 19 Sep 2016, at 03:12, Thiago Macieira wrote:
>
>
Good Morning,
> And, like I said, others may have done the same. See the discussion on the
> Coverity issue.
>
> Please fix.
as Thiago has indicated the following is broken on at least my Ubuntu system:
cd
> On 18 Sep 2016, at 20:40, Thiago Macieira wrote:
Hi!
>> /home/qt-project/coverity/qt5/qtbase/src/plugins/platforms/xcb/qxcbconnectio
>> n.h:689:20: error: 'TabletData' is not a member of 'QXcbConnection'
>>
> On 18 Sep 2016, at 17:12, Marc Mutz wrote:
>
>
> This is another issue. This week's report only contains issues in code built
> by qmake, probably caused by the configure problem you mention.
>
> Last week's report, to which Peppe referred, however, contained all of
>
> On 15 Sep 2016, at 14:51, Giuseppe D'Angelo wrote:
>
> Howdy,
Hi!
>
> while playing around with Coverity Scan with a few colleagues of mine we
> noticed that only qtbase is getting uploaded and therefore checked
> (instead of the complete qt5.git).
>
> I'm
> On 16 Mar 2016, at 07:09, Thiago Macieira wrote:
>
> I'd like to turn off the automatic detection in the Unix configure for Qt
> 5.6.
> This will solve the problem of the failure to compile (with a hammer).
sure
> Holger: do you know any more details about
Hi,
I would like to provide a small status of the coverity builds and ask for some
help. The last weekend
the analysis failed because lower than a threshold of C++ code could be parsed.
The coverity analysis
tool is executed alongside the compiler when building qt5. This has occurred in
the
> On 19 Nov 2015, at 10:41, Welbourne Edward
> wrote:
>
>> The build is done every Saturday on a Ubuntu 14.04 system and
>> the result is then uploaded to coverity
>
> What's the specific URL ?
You will need to join the "project" and then can see the
> On 19 Nov 2015, at 11:40, Welbourne Edward
> wrote:
>
> I take it that's something I can do once the site is back up.
> If not, where do I need to go to do that ?
right.
> Makes sense. I've mostly been contributing fixes, on the release
> branch, and
> On 06 Nov 2015, at 17:45, Knoll Lars wrote:
>
> On 06/11/15 17:38, "Development on behalf of Giuseppe D'Angelo"
> wrote:
Hi,
> To me this points strongly to opt for never unloading plugins.
On 06 Aug 2015, at 18:57, Hausmann Simon simon.hausm...@theqtcompany.com
wrote:
Right, in 5.5 any stale state on the file system is likely to survive. In dev
(new ci) that problem is gone.
Should the test clean this directory? Could the CI log which files were created
during the
13 matches
Mail list logo