Re: LyX 2.3.3 Tarballs
On Sat, Jun 15, 2019 at 05:53:09AM -, Guenter Milde wrote: > This should, IMO, be release-critical. > > The trick is to differentiate these from the tests that change document I have nothing against only critical tests being involved, but at this stage we are not there... Pavel
Re: LyX 2.3.3 Tarballs
On 2019-06-11, Pavel Sanda wrote: > On Tue, Jun 11, 2019 at 12:21:51PM +0200, Kornel Benko wrote: >> Tried to compile with cmake and enabled tests ... ( >> -DLYX_ENABLE_EXPORT_TESTS=ON) > I propose that before cmake tests is considered to be showstopper for release > they do roughly the same as autotools make check (testing various src/../tests > codes, not this development stuff which seems extremely fragile to all sorts > of circumstances). There are actually many ctests doing basic stuff: testing whether examples, documentation and templates compile as advertised/intended. This should, IMO, be release-critical. The trick is to differentiate these from the tests that change document settings and/or compile to different output formats. (The "defaultoutput" test tag should do this but currently has some flaws.) Günter
Re: LyX 2.3.3 Tarballs
On Tuesday, 11 June 2019 14.36.50 WEST José Abílio Matos wrote: > Builds cleanly on Fedora 29 to Rawhide (to be Fedora 31). Actually it also > does on Fedora 28 but that it is at EOL (End of Live) stage. > > https://copr.fedorainfracloud.org/coprs/jamatos/lyx-next/ > > As soon as the release announce is done I will move it to updates-testing > repositories. Just like Jean-Pierre I can tell that all tests passed on all Fedora releases and architectures (i386, x86_64 and aarch64). https://copr.fedorainfracloud.org/coprs/jamatos/lyx-next/build/934304/ You can see the output of the build (in this case for rawhide - F31 on x84_64): https://copr-be.cloud.fedoraproject.org/results/jamatos/lyx-next/fedora-rawhide-x86_64/00934304-lyx/builder-live.log Due to some timing issues the ppc64le (ppc64 Little Endian) servers on copr decided to take some time off. :-) Really, since Sunday that those builders are on strike and are ignoring us so left them out for the moment. :-) -- José Abílio
Re: LyX 2.3.3 Tarballs
Le 11/06/2019 à 18:38, Jean-Pierre Chrétien a écrit : All common manuals compile fine with TL 2019. and 'make check' is successful (9 tests are OK). -- Jean-Pierre
Re: LyX 2.3.3 Tarballs
Am Dienstag, 11. Juni 2019, 22:18:26 CEST schrieb Richard Kimberly Heck: > On 6/11/19 3:19 PM, Kornel Benko wrote: > > Am Dienstag, 11. Juni 2019, 14:11:17 CEST schrieb Richard Kimberly Heck: > >> On 6/11/19 12:57 PM, Kornel Benko wrote: > >>> Am Dienstag, 11. Juni 2019, 14:01:24 CEST schrieb Pavel Sanda: > On Tue, Jun 11, 2019 at 12:21:51PM +0200, Kornel Benko wrote: > > Tried to compile with cmake and enabled tests ... ( > > -DLYX_ENABLE_EXPORT_TESTS=ON) > I propose that before cmake tests is considered to be showstopper for > release > they do roughly the same as autotools make check (testing various > src/../tests > codes, not this development stuff which seems extremely fragile to all > sorts > of circumstances). > > Pavel > > >>> I suppose, you have tried to use the devel tests, still my opinion is > >>> different. > >>> Nobody is forced to enable these tests, but why should we force anybody > >>> to not > >>> be able to run them? > >> What do we need to do to make the run-able? What's missing? > >> > >> Riki > >> > >> > > Attached should be OK. At least, with the mentioned files, the tests are > > running. > > Please go ahead. I'll rebuild the tarballs. > > This won't affect the binaries already built, right? Yes, nothing to do with binaries. It is only some extra data we provide in case a user wants to compile on his own _and_ wants to run some export tests. > Riki > Done at ac724043. Kornel signature.asc Description: This is a digitally signed message part.
Re: LyX 2.3.3 Tarballs
On 6/11/19 3:19 PM, Kornel Benko wrote: > Am Dienstag, 11. Juni 2019, 14:11:17 CEST schrieb Richard Kimberly Heck: >> On 6/11/19 12:57 PM, Kornel Benko wrote: >>> Am Dienstag, 11. Juni 2019, 14:01:24 CEST schrieb Pavel Sanda: On Tue, Jun 11, 2019 at 12:21:51PM +0200, Kornel Benko wrote: > Tried to compile with cmake and enabled tests ... ( > -DLYX_ENABLE_EXPORT_TESTS=ON) I propose that before cmake tests is considered to be showstopper for release they do roughly the same as autotools make check (testing various src/../tests codes, not this development stuff which seems extremely fragile to all sorts of circumstances). Pavel >>> I suppose, you have tried to use the devel tests, still my opinion is >>> different. >>> Nobody is forced to enable these tests, but why should we force anybody to >>> not >>> be able to run them? >> What do we need to do to make the run-able? What's missing? >> >> Riki >> >> > Attached should be OK. At least, with the mentioned files, the tests are > running. Please go ahead. I'll rebuild the tarballs. This won't affect the binaries already built, right? Riki
Re: LyX 2.3.3 Tarballs
Am Dienstag, 11. Juni 2019, 21:55:22 CEST schrieb Pavel Sanda: > On Tue, Jun 11, 2019 at 06:57:27PM +0200, Kornel Benko wrote: > > Am Dienstag, 11. Juni 2019, 14:01:24 CEST schrieb Pavel Sanda: > > > On Tue, Jun 11, 2019 at 12:21:51PM +0200, Kornel Benko wrote: > > > > Tried to compile with cmake and enabled tests ... ( > > > > -DLYX_ENABLE_EXPORT_TESTS=ON) > > > > > > I propose that before cmake tests is considered to be showstopper for > > > release > > I meant *not* to be showstopper... Ah, OK. > > > they do roughly the same as autotools make check (testing various > > > src/../tests > > > codes, not this development stuff which seems extremely fragile to all > > > sorts > > > of circumstances). > > > > > > Pavel > > > > > > > I suppose, you have tried to use the devel tests, still my opinion is > > different. > > Nobody is forced to enable these tests, but why should we force anybody to > > not > > be able to run them? > > If they work why not, what I am saying it's not Richard's job to keep track > of it. > > Pavel Yes, my bad. Should have take care of it. Kornel signature.asc Description: This is a digitally signed message part.
Re: LyX 2.3.3 Tarballs
On Tue, Jun 11, 2019 at 06:57:27PM +0200, Kornel Benko wrote: > Am Dienstag, 11. Juni 2019, 14:01:24 CEST schrieb Pavel Sanda: > > On Tue, Jun 11, 2019 at 12:21:51PM +0200, Kornel Benko wrote: > > > Tried to compile with cmake and enabled tests ... ( > > > -DLYX_ENABLE_EXPORT_TESTS=ON) > > > > I propose that before cmake tests is considered to be showstopper for > > release I meant *not* to be showstopper... > > they do roughly the same as autotools make check (testing various > > src/../tests > > codes, not this development stuff which seems extremely fragile to all sorts > > of circumstances). > > > > Pavel > > > > I suppose, you have tried to use the devel tests, still my opinion is > different. > Nobody is forced to enable these tests, but why should we force anybody to not > be able to run them? If they work why not, what I am saying it's not Richard's job to keep track of it. Pavel
Re: LyX 2.3.3 Tarballs
Am Dienstag, 11. Juni 2019, 14:11:17 CEST schrieb Richard Kimberly Heck: > On 6/11/19 12:57 PM, Kornel Benko wrote: > > Am Dienstag, 11. Juni 2019, 14:01:24 CEST schrieb Pavel Sanda: > >> On Tue, Jun 11, 2019 at 12:21:51PM +0200, Kornel Benko wrote: > >>> Tried to compile with cmake and enabled tests ... ( > >>> -DLYX_ENABLE_EXPORT_TESTS=ON) > >> I propose that before cmake tests is considered to be showstopper for > >> release > >> they do roughly the same as autotools make check (testing various > >> src/../tests > >> codes, not this development stuff which seems extremely fragile to all > >> sorts > >> of circumstances). > >> > >> Pavel > >> > > I suppose, you have tried to use the devel tests, still my opinion is > > different. > > Nobody is forced to enable these tests, but why should we force anybody to > > not > > be able to run them? > > What do we need to do to make the run-able? What's missing? > > Riki > > Attached should be OK. At least, with the mentioned files, the tests are running. Korneldiff --git a/development/Makefile.am b/development/Makefile.am index 1fed26a..f5b218d 100644 --- a/development/Makefile.am +++ b/development/Makefile.am @@ -103,10 +103,18 @@ autotests/CMakeLists.txt \ autotests/check_load.cmake \ autotests/export.cmake \ autotests/ExportTests.cmake \ autotests/keytest.py \ autotests/lyx2lyxtest.cmake \ +autotests/ignoredTests \ +autotests/ignoreLatexErrorsTests \ +autotests/invertedTests \ +autotests/suspendedTests \ +autotests/unreliableTests \ +autotests/lyxStatus.pm \ +autotests/getTempDir.pl \ +autotests/useSystemFonts.pl \ autotests/single-test.cmake \ autotests/xvkbd/CMakeLists.txt \ autotests/xvkbd/findwidget.c \ autotests/xvkbd/resources.h \ autotests/xvkbd/XVkbd-common.h \ signature.asc Description: This is a digitally signed message part.
Re: LyX 2.3.3 Tarballs
On 6/11/19 12:57 PM, Kornel Benko wrote: > Am Dienstag, 11. Juni 2019, 14:01:24 CEST schrieb Pavel Sanda: >> On Tue, Jun 11, 2019 at 12:21:51PM +0200, Kornel Benko wrote: >>> Tried to compile with cmake and enabled tests ... ( >>> -DLYX_ENABLE_EXPORT_TESTS=ON) >> I propose that before cmake tests is considered to be showstopper for release >> they do roughly the same as autotools make check (testing various >> src/../tests >> codes, not this development stuff which seems extremely fragile to all sorts >> of circumstances). >> >> Pavel >> > I suppose, you have tried to use the devel tests, still my opinion is > different. > Nobody is forced to enable these tests, but why should we force anybody to not > be able to run them? What do we need to do to make the run-able? What's missing? Riki
Re: LyX 2.3.3 Tarballs
Am Dienstag, 11. Juni 2019, 14:01:24 CEST schrieb Pavel Sanda: > On Tue, Jun 11, 2019 at 12:21:51PM +0200, Kornel Benko wrote: > > Tried to compile with cmake and enabled tests ... ( > > -DLYX_ENABLE_EXPORT_TESTS=ON) > > I propose that before cmake tests is considered to be showstopper for release > they do roughly the same as autotools make check (testing various src/../tests > codes, not this development stuff which seems extremely fragile to all sorts > of circumstances). > > Pavel > I suppose, you have tried to use the devel tests, still my opinion is different. Nobody is forced to enable these tests, but why should we force anybody to not be able to run them? Kornel signature.asc Description: This is a digitally signed message part.
Re: LyX 2.3.3 Tarballs
Le 10/06/2019 à 21:45, Richard Kimberly Heck a écrit : Here: http://ftp.lyx.org/pub/lyx/devel/lyx-2.3/ Please test and prepare binaries. Compiles fine on Debian Stretch with the following configuration : Host type: x86_64-pc-linux-gnu Special build flags: build=release std-regex use-hunspell Bundled libraries:boost mythes C++ Compiler:g++ (6.3.0) C++ Compiler flags: -fPIC -O2 -std=c++14 C++ Compiler user flags: Linker flags: Linker user flags: Qt Frontend: Qt version: 5.7.1 Packaging: posix LyX binary dir: /usr/local/bin LyX files dir: /usr/local/share/lyx-2.3.3 All common manuals compile fine with TL 2019. -- Jean-Pierre
Re: LyX 2.3.3 Tarballs
Am 10.06.2019 um 21:45 schrieb Richard Kimberly Heck : > > Here: > > http://ftp.lyx.org/pub/lyx/devel/lyx-2.3/ > > Please test and prepare binaries. It compiles and runs on Mac. I’ve tried to typeset the users guide and it worked. The binary distribution is ready. Stephan
Re: LyX 2.3.3 Tarballs
On Monday, 10 June 2019 20.45.22 WEST Richard Kimberly Heck wrote: > Here: > > http://ftp.lyx.org/pub/lyx/devel/lyx-2.3/ > > Please test and prepare binaries. > > Riki Builds cleanly on Fedora 29 to Rawhide (to be Fedora 31). Actually it also does on Fedora 28 but that it is at EOL (End of Live) stage. https://copr.fedorainfracloud.org/coprs/jamatos/lyx-next/ As soon as the release announce is done I will move it to updates-testing repositories. -- José Abílio
Re: LyX 2.3.3 Tarballs
On Mon, Jun 10, 2019 at 03:45:22PM -0400, Richard Kimberly Heck wrote: > Here: > > http://ftp.lyx.org/pub/lyx/devel/lyx-2.3/ > > Please test and prepare binaries. Compiles and runs with qt 4.8.5, gcc 4.9.4 && Qt 5.7.1, gcc 6.3.0. Pavel
Re: LyX 2.3.3 Tarballs
On Tue, Jun 11, 2019 at 12:21:51PM +0200, Kornel Benko wrote: > Tried to compile with cmake and enabled tests ... ( > -DLYX_ENABLE_EXPORT_TESTS=ON) I propose that before cmake tests is considered to be showstopper for release they do roughly the same as autotools make check (testing various src/../tests codes, not this development stuff which seems extremely fragile to all sorts of circumstances). Pavel
Re: LyX 2.3.3 Tarballs
Am Dienstag, 11. Juni 2019, 10:51:30 CEST schrieb Jean-Marc Lasgouttes: > Le 10/06/2019 à 21:45, Richard Kimberly Heck a écrit : > > Here: > > > > http://ftp.lyx.org/pub/lyx/devel/lyx-2.3/ > > > > Please test and prepare binaries. > > > > Tested on ubuntu 16.04 gcc/clang, Qt 4.8.7/5.5.1. > > Seems to work well. > > JMarc > Tried to compile with cmake and enabled tests ... ( -DLYX_ENABLE_EXPORT_TESTS=ON) ... CMake Error at development/autotests/ExportTests.cmake:204 (file): file STRINGS file "/usr2/src/lyx/lyx-2.3.3/development/autotests/invertedTests" cannot be read. Same for ignoredTests, suspendedTests, unreliableTests and ignoreLatexErrorsTests. The result: -- Configuring incomplete, errors occurred! Setting -DLYX_ENABLE_EXPORT_TESTS=OFF, compiles fine and creates a package too on Ubuntu. Kornel signature.asc Description: This is a digitally signed message part.
Re: LyX 2.3.3 Tarballs
Le 10/06/2019 à 21:45, Richard Kimberly Heck a écrit : Here: http://ftp.lyx.org/pub/lyx/devel/lyx-2.3/ Please test and prepare binaries. Tested on ubuntu 16.04 gcc/clang, Qt 4.8.7/5.5.1. Seems to work well. JMarc
Re: LyX 2.3.3 Tarballs
On Mon, Jun 10, 2019 at 03:45:22PM -0400, Richard Kimberly Heck wrote: > Here: > > http://ftp.lyx.org/pub/lyx/devel/lyx-2.3/ > > Please test and prepare binaries. Did a quick test. It compiles well for me on Ubuntu 19.04, and I could compile the three help documents that I tried. Scott signature.asc Description: PGP signature
LyX 2.3.3 Tarballs
Here: http://ftp.lyx.org/pub/lyx/devel/lyx-2.3/ Please test and prepare binaries. Riki
