[Libreoffice-bugs] [Bug 125320] - sporadic fail! - combination of autocalculate and shared formulae still broken in 6.3.0.0.alpha1+ with threaded off

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=125320

--- Comment #10 from Telesto <telesto at surfxs.nl> ---
(In reply to b. from comment #9)
I still hoping Michael being able be of some assistance here. He does care
about this topic and belongs to they higher echelons of the project. However
major problem is there is not much to 'work with'.

Sudden miscalculations are pain. There however multiple causes: OpenCL,
multi-threaded or iterations and or/the specific document (or order of doing
things).

And I'm admitting that the user isn't ideal person to verify calculations or to
figure out the issue. And that there number of variables involved which don't
make it easy to track down issues :-(

I'm not a heavy Calc user myself. So working with the stuff I'm able to
reproduce (and bibisect). They rest are elusive bugs. I wouldn't be surprised
if there some flaw with calculations somewhere (or at multiple places).
However, without an example there is not much to be done about it.

Also no idea if there are (stress testing) models available to verify results
with different OS'es Windows/Linux/Mac with different configurations (OpenCL
only, Multi-threaded only or both enabled to verifying results). Maybe even on
different configurations (Amd/Intel). 

Also no clue if OpenCL wills stick around, or will be phased-out in favor of
multi-threaded calculations. With limited resources I prefer to 'stick' with
not to many options which aren't 'properly' maintained. 

[Off-topic: Also referring to Skia, I hope all environments (and all backends)
will use it someday. It's slightly frustrating that certain issues are limited
to the Windows environment. FWIW: I would prefer GDI to be moved the expert
settings for 7.1. As 'testing backend only. Performance (especially related to
images/shapes/bitmaps) starting to become awful already as far I noticed (and
not reporting anything about that as it will be gone anyway). But bit out of
scope here

However, I tend to agree that 'reports' without a showcase, not being really
helpful. And they bug tracker isn't the ideal place for 'concerns' or hunches.
[of course there are no 'hard' rules what belongs to the bug tracker and what
not, but tends to go to the NOTOURBUG area] 
OTOH, dropping out the bug tracker somehow suggests nothing being wrong; and
pretending nothing is going on.

I do get you're frustration. I'm pushing for bit more attention for user
experience in global; wishing for a bit more polished product in general
(quality control). In my case mostly orientated at Writer/Impress. As see
reproducible problems there.  
And not knowing much about Calc and the calculation bugs being bit problematic
to get hold on :-). But Calc belong to quality control also.

However this isn't easy thing to archive, based on how things are organized
around here. There is no central organization. It's decentralized organization
with different people working together (somehow) with different agenda's,
interest, concerns (and budgets). At the end everything is monetized in
expenses an revenue.

Anyhow. Michael, any idea how approach/tackle/handle this topic here. I don't
want to dismiss the calculation issues of regular QA contributor. OTOH, not big
fan of bugs reports leading to nowhere, practically speaking. Or a way how b.
can help out. Say logging debug information. They issue must be show up
somewhere?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20201014/86e70e42/attachment-0001.htm>