Re: [musl] Re: parse-datetime test failure

On 11/11/20 8:07 PM, Rich Felker wrote: Thanks. I believe you've just re-discovered a known bug that's fixed in musl commit 8ebc853d37c80f0f236cc7a92cb0acc6aace, which will be included in the upcoming 1.2.2 release. Yes, thanks, that looks exactly right. It's *so* nice to have bugs fixed be

Re: [musl] Re: parse-datetime test failure

On Wed, Nov 11, 2020 at 07:38:00PM -0800, Paul Eggert wrote: > On 11/11/20 8:20 AM, Bruno Haible wrote: > >It works fine on Alpine Linux 3.7 (32-bit, 64-bit) and 3.9 (64-bit). > > > >On Alpine Linux 3.10 and 3.12 (64-bit) it fails: > >../../gltests/test-parse-datetime.c:448: assertion 'result.tv_se

Re: parse-datetime test failure

On 11/11/20 8:20 AM, Bruno Haible wrote: It works fine on Alpine Linux 3.7 (32-bit, 64-bit) and 3.9 (64-bit). On Alpine Linux 3.10 and 3.12 (64-bit) it fails: ../../gltests/test-parse-datetime.c:448: assertion 'result.tv_sec == 1 * 60 * 60 + 2 * 60 + 3 && result.tv_nsec == 123456789' failed Abo

Re: CI/CD testing of gnulib?

Hi Simon, > As you can see above, Alpine exists. Indeed, that would be a useful platform to add. Thanks for the pointer; it should be easy. Though, it will require adding a second CI project, since the current CI project already eats up 75% of the allowed Gitlab limit of 400 minutes per month. >

Re: CI/CD testing of gnulib?

Bruno Haible writes: > Hi Simon, > >> I'm wondering if there is any CI/CD testing of gnulib for >> different platforms? > > There is some automated CI testing done one gitlab.com. Tim, can you please > answer my question from [1]? Thanks -- indeed doing this on GitLab would be easy, and I'm happ

Re: CI/CD testing of gnulib?

Hi Dago, > I’d happily set up buildbot testing for Solaris. What should be specifically > executed for the CI test? The typical commands are: - git clone --depth 1 https://git.savannah.gnu.org/git/gnulib.git - cd gnulib - ./gnulib-tool --create-testdir --dir=./testdir --single-config

Re: CI/CD testing of gnulib?

Hi Bruno, Am 11.11.2020 um 17:21 schrieb Bruno Haible : > * Some platforms are not covered by CI testing platforms (e.g. AIX, Solaris, >Minix, but also Alpine Linux). […] > I occasionally do testing of all of gnulib or, more frequently, the POSIX > related part of gnulib. But it's really occa

Re: parse-datetime test failure

Hi Simon, > I noticed the test-parse-datetime fails on Alpine Linux, and > probably has failed since 2017-04-26 when the "Outlandishly-long time > zone abbreviations" test was added. (It could also be a recent > regression, of course.) It works fine on Alpine Linux 3.7 (32-bit, 64-bit) and 3.9 (

Re: CI/CD testing of gnulib?

Hi Simon, > I'm wondering if there is any CI/CD testing of gnulib for > different platforms? There is some automated CI testing done one gitlab.com. Tim, can you please answer my question from [1]? But it does not do so on multiple platforms, because * The CI systems for different platforms ha

[modules / vcs-to-changelog] Wrong filename path if spaces in file name.

Hi, this is a sample output I get: 2020-05-03 THBO COMMIT: 1d02a74a93dfcb7822a0ddb1bb003db18fae4c72 Message sample. * Modele/Datawarehouse/GesCom/Vente.mdl: Modified. * Modele/Datawarehouse/Gescom: Modified. * Modele/Datawarehouse/Gescom: Modified. * Modele/Gescom1/F: Modified. * Modele/Gesc

CI/CD testing of gnulib?

Hello. I noticed the test-parse-datetime fails on Alpine Linux, and probably has failed since 2017-04-26 when the "Outlandishly-long time zone abbreviations" test was added. (It could also be a recent regression, of course.) I don't have cycles to work on that particular bug, but I'm wondering i