[Development] Done: Codereview maintenance on Monday 4-Sep 5:00 am UTC
Gerrit is back online. From: Development on behalf of Jukka Jokiniva via Development Date: Monday, 4. September 2023 at 7.52 To: qt-dev Subject: [Development] Reminder: Codereview maintenance on Monday 4-Sep 5:00 am UTC The maintenance break will start in 10 minutes From: Development on behalf of Jukka Jokiniva via Development Date: Thursday, 31. August 2023 at 12.41 To: qt-dev Subject: [Development] Codereview maintenance on Monday 4-Sep 5:00 am UTC Hi all, There will be a maintenance break on the codereview.qt-project.org on Monday 4-Sep 5:00 am – 6:00 am UTC. --Jukka Jokiniva, Gerrit Admin -- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] CI failing due to ASan tst_selftest
On Sonntag, 27. August 2023 17:42:58 CEST Thiago Macieira wrote: > On Sunday, 27 August 2023 02:35:39 PDT Ulf Hermann via Development wrote: > > I've seen this one before. I suspect certain versions of fontconfig have > > an internal memory leak. For me, it fixed itself after an upgrade of > > some packages. Can we install debug symbols for fontconfig on the > > respective platforms? Then we could see a proper stack trace. > > That rings a bell, indeed. > > But I'm not convinced it's a leak, as opposed to reachable memory that > wasn't freed before exit. LSAN doesn't do a still-reachable analysis. > I also don't think debug symbols will help here, since this is coming from > the dynamic symbols of the module in question, not from the debug info. If > you look at the qFatal() leak I fixed, you see that there are unknown > QtCore frames printed, meaning the stack trace didn't use debug symbols. By default, LSAN will rely purely on frame pointers. As such, if fontconfig is compiled without them, the backtraces will be unhelpful. You can force usage of .eh_frame et al by exporting LSAN_OPTIONS=fast_unwind_on_malloc=false But this option is really very slow, as the sanitizers don't use a caching unwinding library. I do not recommend running tests with this always enabled, but for one-off investigations it should be useful. Hope that helps -- Milian Wolff m...@milianw.de http://milianw.de signature.asc Description: This is a digitally signed message part. -- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Monthly CI maintenance break - September (Mon, Sep 4th 2023)
This starts NOW From: Ville-Pekka Karhu Sent: Monday, August 28, 2023 09:43 To: Qt development mailing list Subject: Monthly CI maintenance break - September (Mon, Sep 4th 2023) Hi, We’ll have our scheduled maintenance break on next Monday (4th of September). We’ll begin our work at 5:00 UTC and you can prepare for 6 hours of CI not working. -- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
[Development] Reminder: Codereview maintenance on Monday 4-Sep 5:00 am UTC
The maintenance break will start in 10 minutes From: Development on behalf of Jukka Jokiniva via Development Date: Thursday, 31. August 2023 at 12.41 To: qt-dev Subject: [Development] Codereview maintenance on Monday 4-Sep 5:00 am UTC Hi all, There will be a maintenance break on the codereview.qt-project.org on Monday 4-Sep 5:00 am – 6:00 am UTC. --Jukka Jokiniva, Gerrit Admin -- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
