On Thu, 26 Oct 2023 at 16:34, Miklos Vajna wrote:
> 26 Killed by the kill-wrapper
> gerrit_linux_clang_dbgutil
> 28 UITest_sw_navigatorgerrit_linux_clang_dbgutil
> + in terms of test failures, unfortunately again high number of
> killed jobs + sw_navigator failure
On Thu, 31 Aug 2023 at 17:30, Miklos Vajna wrote:
> * Jenkins / CI update (Cloph)
> + had a high number of failures this week (Cloph)
>
I have disabled 3 pieces of UITest code, which should greatly reduce
the number of outright UITest failures and "build timed out" we see.
On Thu, 27 Apr 2023 at 16:55, Miklos Vajna wrote:
> * Update Microsoft Visual Studio baseline? (NoelG)
>+ open question: what benefits would that bring?
> + also: should we require it?
> + one benefit: only toolset for arm natively is 2022
>+ can't remember any reason right now
On Fri, 27 Jan 2023 at 09:26, Miklos Vajna wrote:
> * Crash Testing (Caolan)
> + 117(+13) import failure, 5(+1) export failures
>
> - help with Calc threaded issues are appreciated, see the recent dev
> mailing list post
>
>
Clang's TSAN says there is at least one data-race when doing
> * What’s cooking (Miklos)
> + Noel looked at UNO-level weak references, performance → found a
> different solution for a11y
>
>
Our a11y is fundamentally slow because it always builds a parallel object
hierarchy of ~everything, UI and document model.
And because it makes extensive use of weak
On Thu, 8 Jul 2021 at 16:29, Miklos Vajna wrote:
> 8 CppunitTest_sw_core_undogerrit_windows
> 9 CppunitTest_writerperfect_writergerrit_windows
> 22 CppunitTest_sc_uicalc gerrit_windows
>
>
Can anyone else trigger these? I've tried and I c
ne:
commit 2176084192dc46a1ef5d6dd79effa5cd5d1dcca2
Author: Noel Grandin
Date: Thu Jun 17 13:38:07 2021 +0200
fix potential write-after-free in RecentDocsView
>
>
___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
C
On Thu, 14 Jan 2021 at 17:45, Miklos Vajna wrote:
> * Crash Testing (Caolan)
> + 16 ossfuzz issues, 12 Timeouts
> + lots of new issues → exception when reading the past the end of
> the stream
> + not sure if this is improving things in practice
>
>
I'm not deeply attached to SvSt
On Thu, 14 May 2020 at 16:51, Miklos Vajna wrote:
> + 'performance problem with plenty comments' still in 6.3 alpha1,
> *only after save of file/autosave*
> + https://bugs.documentfoundation.org/show_bug.cgi?id=125619
> + Armin?
> + the problem is that
On Thu, 16 May 2019 at 17:04, Michael Meeks
wrote:
> * ItemSet re-work (Armin)
>+ most of items are sorted in the item-pools (Armin)
> + not inside the item-sets.
> + in the item pools: just in a vector
> + only compare, not < operator – usually not sorted.
>
Note that I ha
On Sun, 24 Feb 2019 at 22:04, Samuel Thibault wrote:
> The fact that even the C UI strings may change is a concern indeed. We
> however don't really have another way to identify widgets, do we? (we
> don't want to identify them structurally, that'd be even less stable)
>
>
The LibreOffice python
So yes, the focus information would be fairly easy to expose to the python
UI test infrastructure.
And yes, it would be good to limit the number of different frameworks we
use for testing (we already have 4 - C++ direct, C++ via UNO, Java via UNO,
python via UNO)
However, the current python UI te
e
On 7 June 2018 at 16:46, Michael Meeks wrote:
> + also looked at Windows build / CPU
> + total time ~50mins
> + 5 minutes at the begin – checkout/dep gen.
> + 8 min in middle & end – just 1 CPU core.
> + 20mins – with just 1 core.
> + so shoul
On 1 February 2018 at 18:54, Jan Holesovsky wrote:
>
>
> * Budgeting (Thorsten)
> + collecting wish-lists:
> + get some fast new Macs and host at Manitu
> + gerrit updates
> + other ideas for development topics ?
>
>
SSDs for existing macs.
SSD for gerrit (I often find it
On 7 October 2016 at 13:21, Jan Iversen wrote:
> We should really start looking at ways to increase the number, I know
> there are open source packages that can do that.
>
> Anyhow, nothing important was missed.
>
Either that, or the person starting the call needs to have a Google Apps
for Busi
On 10 December 2015 at 18:22, Michael Meeks wrote:
> * Pending Action Items:
> + get callgrind trace of SVG rendering in tdf#82214 (JMux)
>
I have a patch in progress which may improve that:
https://gerrit.libreoffice.org/#/c/20589/
___
List Name: L
On 2015-05-29 02:37 AM, Bjoern Michaelsen wrote:
pragmatically splitting up the first four:
https://gerrit.libreoffice.org/#/c/15959/
brings 'make check' down to 2m6s on big Bertha. For comparison:
Nice work! Can't wait to see that in.
And I have some ideas about speeding up the Java t
> takes 15mins to run 'make check' (Michael)
Wasn't someone going to look at speeding that up? Make check is not
currently making very good use of multiple cores and it has a long tail
where only one or two cores are busy.
On Thu, 28 May 2015 at 18:38, Norbert Thiebaud wrote:
> On Thu, May 28,
On Fri, Mar 6, 2015 at 1:59 PM, Michael Meeks
wrote:
>
>
>
> * Jenkins update (Norbert)
> + mostly green
>+ queue 64 patches long, Chris pushed a 20x deep series 3x in a row.
Is it possible to
(a) have a way of cancelling stuff in the queue if we need to re-push
patches to gerrit?
an
On 2014-11-13 06:13 PM, Michael Meeks wrote:
* library bloat (Michael S)
+ not really an issue for release builds - --enable-mergelibs
+ big library + --enable-symbols -> OOM
+ especially problematic CppuniTests with use_library_objects
+ perhaps a barrier to entry to
On 2013-12-05 19:23, Michael Meeks wrote:
+ attach a callgrind profile for 'expert config' to bug (Kendy)
[ could make it experimental later if necessary ]
https://bugs.freedesktop.org/show_bug.cgi?id=72125
I've pushed a small cleanup related to this code to gerrit:
h
On 2013-07-29 15:31, Stephan Bergmann wrote:
However, I do not know how to trigger that (Windows-specific anyway)
code, but I would like to be able to verify that the new code works as
intended (whether or not the old code did) before backporting this to
libreoffice-4-0 and -4-1.
Normally,
this has some nice XSLT explanations
http://www.w3schools.com/xsl/
with explanations and an on-line executor here
http://www.w3schools.com/xsl/xsl_examples.asp
The hardest part is normally working out the XPath expressions to use
in the match values.
_
On Thu, Jul 19, 2012 at 5:50 PM, Michael Meeks wrote:
>
> * 4.0 - when to call it that ? (Kendy)
> + http://wiki.documentfoundation.org/Development/LibreOffice4
> + too much to do in one six-month section
IMNSHO, most of the stuff on that page can be accomplished i
HI
It would be nice if the gerrit emails had this in the header:
To: libreoff...@lists.freedesktop.org,
SO that my mailing list filters picked it up as belonging to the libreoffice
mailing list.
Thanks, Noel Grandin
On 2012-07-04 14:38, Bjoern Michaelsen wrote:
So whenever you do something
On Sat, Jun 30, 2012 at 2:35 AM, Joel Madero wrote:
> One of my mein concerns is that we aren't keeping up with bug reports so we
> may close a bug at eol without anyone from QA or any developer ever looking
> at it. To me this seems unfair to the reporter.
>
It is a little rough but it's a reali
On 2012-06-29 14:47, Caolán McNamara wrote:
I looked through some of these, some patches are just experimental
stuff or debugging patches or obsolete stuff.
Maybe we should have some way of marking bugs in "in-progress" or
"experimental" ?
Maybe just push bugs that have incomplete patches in
I'm curious - what does the AA tag mean?
On 2012-05-10 18:47, Michael Meeks wrote:
AA: + switch to them in master if no reply (Caolan)
AA: + Kohei needs to ack / sign off for Thorsten (Kohei)
AA: + get Alexander commit access& give a free hand (Michael)
AA: + loo
On 2012-03-15 14:31, Pedro Lino wrote:
As a general conclusion I think we are all doing the best given the
limited human resources and the scarcity of our most valuable
resource: time!
It is because we do CARE about this project that we complain about the
short testing times AND the regress
People who think there should be zero regressions are welcome to donate the
necessary time and financial resources to
make it happen.
Michael Meeks wrote:
> Hi Pedro,
>
> On Sat, 2011-12-10 at 11:46 +, Pedro Lino wrote:
>> This isn't simply a matter of checking and reporting bugs. It involve
Duration timers are best implemented using the system's monotonic
clock.In Java, this is System.nanoTime(),under linux, this is
clock_gettime(CLOCK_MONOTONIC),under windows, it is GetTickCount()
On Tue, Oct 25, 2011 at 17:40, Michael Meeks wrote:
>
> On Tue, 2011-10-25 at 13:54 +0100, Michael Meek
31 matches
Mail list logo
