This is a metabug blocked by all test failures of: - complex tests - unoapi tests on master. If you find an active test failing, please: 1) Create a bug - see the examples linked below as templates - important is the "complextest"/"unoapitest" whiteboard status - mark it as a blocker to this bug 2) deactivate the bug on master, see: - http://cgit.freedesktop.org/libreoffice/filters/commit/?id=affcdcd51ae9b4e5f251bb37be247fcd0473eb38 (complex tests) - http://cgit.freedesktop.org/libreoffice/writer/commit/?id=99e66bd8e02bfa1d2327820b1438272ca7956a4f (unoapi tests) As of 2001-03-24 the following modules are clean: comphelper editeng framework padmin sfx2 sot svl svtools svx sw toolkit tools unoxml xmloff vbahelper There should be no tests failing from these modules. If you find one do, the bug has been recently introduced. Please file a bug as described above with additional "testregression" in whiteboard. If you find other modules clean (or made it clean by deactivating tests), please add a comment here, so that we can easily identify regressions. complextest bug example: https://bugs.freedesktop.org/show_bug.cgi?id=35668 unoapitest bug example: https://bugs.freedesktop.org/show_bug.cgi?id=35660
Adding EasyHack as the disabling of failing tests is easy to do.
As of 2011-03-26 additionally these modules are clean: base jurt linuistic sal stoc Unfortunately these tests fail and need to be disabled and need a bug filed: forms/qa/unoapi ucb/qa/unoapi These test hang and need to be disabled for now: forms/qa/complex/forms configmgr/qa/unoapi sd/qa/unoapi ucb/complex/ucb ucb/qa/unoapi qadevOOo/qa/unoapi chart2/qa/unoapi unotools/qa/complex/tempfile qadevOOo/qa/unoapi starmath/qa/unoapi Likely, they can be reenabled once oosplash.bin takes notice of LO shutting down.
All tests have either been reenabled or disabled with a bug filed. subsequenttest is thus clean as of now (2011-03-27). If any test fails now it is a regression. Please report!
see also: http://nabble.documentfoundation.org/subsequentcheck-in-gbuild-modules-please-help-us-to-continuously-QA-LO-td2729991.html http://nabble.documentfoundation.org/gbuild-subsequentcheck-is-clean-td2731177.html
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
An EasyHack should have been checked by developers and thus is confirmed regardless of age. Moving back to NEW from NEEDINFO again. Sorry for the hassle.
Deteted "Easyhack" from summary
adding LibreOffice developer list as CC to unresolved EasyHacks for better visibility. see e.g. http://nabble.documentfoundation.org/minutes-of-ESC-call-td4076214.html for details
Removing EasyHack for now, this one doesnt seem to be hugely attractive to newcomers.
Migrating Whiteboard tags to Keywords: (DifficultyInteresting SkillTest SkillCpp) [NinjaEdit]
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.4.1 or 5.3.6 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170929
As this bug is supposed to be a meta bug, there is no reproduce needed. Or are the sub-bugs no longer valid?