Hi again!
The gerrit problems we've seen (example below (pardon for top posting with
Outlook)) are potentially fixed. The problem was found to be in the AWS VM.
Following actions were made to remedy the situation:
* Port range increased to allow more connections
* Mount options adjusted
Hi
This problem was fixed for now. We have the CI running again since yesterday
afternoon. The system needed a cold boot of the server to update all disk
related info after our cleanup. Free space etc were reported incorrectly before
that.
To avoid this, we should never ever let the disk get 1
Hi all,
There is only a bit more than a month to Qt 5.11 feature freeze, see
https://wiki.qt.io/Qt_5.11_Release . So at this point we should already know if
there will be some new submodule modules in Qt 5.11. We are doing packaging
confs etc for 5.11 now so please inform me immediately if ther
Thiago Macieira wrote:
> To build? At least 8 GB of RAM and please use a 64-bit toolchain. You may
> compile for 32-bit, but you need to use a 64-bit linker executable.
I haven't tried 5.10.0 yet, but 5.9.3 built fine with the 32-bit toolchains
we have in our Fedora 32-bit buildroots (i686 and ar
On quinta-feira, 21 de dezembro de 2017 18:57:15 -02 Toan Pham wrote:
> On my t2 sandbox environment, It only has 3G of RAM and that webengine
> build stopped because it ran out of memory.
>
> Does anyone know the minimal memory requirement to build qt w/ webengine.
To build? At least 8 GB of RAM
Sorry for so much email noise,
On my t2 sandbox environment, It only has 3G of RAM and that webengine
build stopped because it ran out of memory.
Does anyone know the minimal memory requirement to build qt w/ webengine.
thanks,
[10013] 0 10013 1785 102 1 0
Hi all,
How do I add an include path (/usr/X11/include) to chromium build.
Not sure why qtwebengine did not detect include path /usr/X11/include
before starting the build. thanks
[1878/11462] CXX obj/skia/skia/SkFontConfigInterface_direct.o
FAILED: obj/skia/skia/SkFontConfigInterface_direct
On quinta-feira, 21 de dezembro de 2017 14:53:35 -02 René J.V. Bertin wrote:
> I'm pretty sure `sysctl hw.model` doesn't return anything that starts with
> Mac when you're not on a Mac though?
Entirely irrelevant, since it would tell you what you're running on, not what
you're compiling for.
--
Hi all,
AFAIU, some time ago Coin considered ps1 script to be failed its exit code was
non-null (e.g, Exit(1) certainly aborted further provisioning process).
Now I see that Exit(1) is ignored (see [1]). What is the correct way now, throw
exception?
[1]
https://testresults.qt.io/coin/api/resu
On Thursday December 21 2017 20:19:03 Konstantin Tokarev wrote:
>> I'm pretty sure `sysctl hw.model` doesn't return anything that starts with
>> Mac when you're not on a Mac though?
>
>Are you trying to distinguish it from PureDarwin?
No, in theory that command should always return the identific
21.12.2017, 19:53, "René J.V. Bertin" :
> On Thursday December 21 2017 16:25:02 Jake Petroules wrote:
>
>> > Possibly: just `uname` returns Darwin. That should certainly work for the
>> desktop OS, but I have no way of checking what it returns on other Apple OSes
>>
>> they all return "Darwin"
On Thursday December 21 2017 16:25:02 Jake Petroules wrote:
> > Possibly: just `uname` returns Darwin. That should certainly work for the
> > desktop OS, but I have no way of checking what it returns on other Apple
> > OSes
>
> they all return "Darwin"
Figures...
> > (and if the Carbon.framew
> On Dec 21, 2017, at 3:57 AM, René J.V. Bertin wrote:
>
> On Thursday December 21 2017 13:47:34 Konstantin Tokarev wrote:
>
>> Check uname maybe?
>
> Possibly: just `uname` returns Darwin. That should certainly work for the
> desktop OS, but I have no way of checking what it returns on othe
both are known and fixes are available.
https://codereview.qt-project.org/#/c/215113/
https://codereview.qt-project.org/#/c/215046/
— Liang
> On 21 Dec 2017, at 14:17, Ulf Hermann wrote:
>
>> You have probably already noticed this, but here’s an email notifying
>> you that we’re on it. Our Ope
You have probably already noticed this, but here’s an email notifying
you that we’re on it. Our OpenNebula isn’t able to clone any new virtual
machines, complaining that the disk is full even though it isn’t. As
said…we continue investigating.
In addition to that we suddenly get failures when co
Hi
You have probably already noticed this, but here's an email notifying you that
we're on it. Our OpenNebula isn't able to clone any new virtual machines,
complaining that the disk is full even though it isn't. As said...we continue
investigating.
Regards,
-Tony
__
On quinta-feira, 21 de dezembro de 2017 04:47:34 CST Konstantin Tokarev wrote:
> > Hi,
> >
> > Here's a silly one: configuring Qt for building on my Linux rig I was told
> > that I needed Xcode, and how to get it. :)
> >
> > Long story short, it turns out that the configure script determines
> >
On Thursday December 21 2017 13:47:34 Konstantin Tokarev wrote:
> Check uname maybe?
Possibly: just `uname` returns Darwin. That should certainly work for the
desktop OS, but I have no way of checking what it returns on other Apple OSes
(and if the Carbon.framework exists there).
R.
__
2017-12-21 11:37 GMT+01:00 Jani Heikkinen :
> With Qt 5.11 it seems we can finally drop MSVC2013 so we could
> "temporarily" add MinGW 64 bit pre-build binaries in our packages in
> addition to 32 bit ones and remove 32 bit MinGW pre-built binaries from
> 5.12 onwards. Making this decision now wou
> Hi,
>
> Here's a silly one: configuring Qt for building on my Linux rig I was told
> that I needed Xcode, and how to get it. :)
>
> Long story short, it turns out that the configure script determines whether
> it's building on Mac by checking if the Carbon framework exists in the
> designa
Hi Jani,
+1 from my side for doing the move to 64bit MinGW in two steps.
Cheers,
Lars
> On 21 Dec 2017, at 11:37, Jani Heikkinen wrote:
>
> Hi all,
>
> There is open suggestion (https://bugreports.qt.io/browse/QTBUG-35288) to
> start delivering MinGW 64 bit pre-built binaries. This has been
Hi all,
There is open suggestion (https://bugreports.qt.io/browse/QTBUG-35288) to start
delivering MinGW 64 bit pre-built binaries. This has been requested several
times in mails, blog comments etc. We have discussed this earlier, last time
with Qt 5.10 where I proposed that we could replace 32
Hi,
Here's a silly one: configuring Qt for building on my Linux rig I was told that
I needed Xcode, and how to get it. :)
Long story short, it turns out that the configure script determines whether
it's building on Mac by checking if the Carbon framework exists in the
designated location. And
> On onsdag 20. desember 2017 17.00.18 CET Konstantin Tokarev wrote:
>
>> I'm repeatedly getting this error:
>>
>> Failed to provision template 'qtci-linux-Ubuntu-16.04-x86_64-1-b46ac1':
>> Failed repeatedly to launch build/test agent
>
> This means it never actually did any work because it eit
> On 21-Dec-2017, at 2:52 PM, Albert Astals Cid
> wrote:
>
> I see a big-ish problem that is that it uses QtQuick so it can't really go
> into qtbase where the current printing dialog lives, so if this was to be
> accepted the printing module would need to split off from qtbase (no idea if
El dijous, 21 de desembre de 2017, a les 10:14:14 CET, Rithvik Patibandla va
escriure:
> Hi
Hi
> This summer, OpenPrinting [1] has created a Common Print Dialog project via
> the Google Summer of Code (2017) program to improve the experience of
> printing in Linux systems with a modern UI and ba
Hi
This summer, OpenPrinting [1] has created a Common Print Dialog project via the
Google Summer of Code (2017) program to improve the experience of printing in
Linux systems with a modern UI and backend APIs that will be maintained by the
OpenPrinting org (the idea can be found here [2]). I am
On onsdag 20. desember 2017 17.00.18 CET Konstantin Tokarev wrote:
> I'm repeatedly getting this error:
>
> Failed to provision template 'qtci-linux-Ubuntu-16.04-x86_64-1-b46ac1':
> Failed repeatedly to launch build/test agent
This means it never actually did any work because it either didn't g
28 matches
Mail list logo