Flaky kcodecs test depending on qt configuration

2013-10-23 Thread Sune Vuorela
Hi Depending on the Qt configuration (built with or without ICU), the KCharsetsTest::testEncodingNames() test fails (in the #if) block. If Qt built with ICU, the tests succeeds and the ISO 8859-16, jis7 and winsami2 codecs are as expected not found. If Qt is built without ICU, those codecs are

Re: Flaky kcodecs test depending on qt configuration

2013-10-23 Thread Kevin Ottens
Hello, On Wednesday 23 October 2013 21:43:59 Sune Vuorela wrote: > Depending on the Qt configuration (built with or without ICU), the > KCharsetsTest::testEncodingNames() test fails (in the #if) block. > > If Qt built with ICU, the tests succeeds and the ISO 8859-16, jis7 and > winsami2 codecs ar

Re: Flaky kcodecs test depending on qt configuration

2013-10-28 Thread John Layt
On Thursday 24 Oct 2013 07:35:48 Kevin Ottens wrote: > Hello, > > On Wednesday 23 October 2013 21:43:59 Sune Vuorela wrote: > > Depending on the Qt configuration (built with or without ICU), the > > KCharsetsTest::testEncodingNames() test fails (in the #if) block. > > > > If Qt built with ICU, th

Re: Flaky kcodecs test depending on qt configuration

2013-11-01 Thread David Faure
On Wednesday 23 October 2013 21:43:59 Sune Vuorela wrote: > Hi > > Depending on the Qt configuration (built with or without ICU), the > KCharsetsTest::testEncodingNames() test fails (in the #if) block. > > If Qt built with ICU, the tests succeeds and the ISO 8859-16, jis7 and > winsami2 codecs ar

Re: Flaky kcodecs test depending on qt configuration

2013-11-01 Thread Sune Vuorela
On 2013-11-01, David Faure wrote: > On Wednesday 23 October 2013 21:43:59 Sune Vuorela wrote: >> Hi >> >> Depending on the Qt configuration (built with or without ICU), the >> KCharsetsTest::testEncodingNames() test fails (in the #if) block. >> >> If Qt built with ICU, the tests succeeds and the