public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Dimitar Dimitrov <dimitar@dinux.eu>
To: jdoubleu <hi@jdoubleu.de>
Cc: newlib@sourceware.org
Subject: Re: [PATCH] add tests for tzset(3)
Date: Sun, 10 Apr 2022 11:43:05 +0300	[thread overview]
Message-ID: <YlKYmZ0oNLitMT2b@kendros> (raw)
In-Reply-To: <569f6ec3-6bc8-8170-c1fb-ed946020e258@jdoubleu.de>

On Thu, Apr 07, 2022 at 05:58:27PM +0200, jdoubleu wrote:
> Hi,
> 
> I've finally created tests for tzset(3). They test the POSIX timezone string
> compliance.
> 
> This patch is intended to be applied after Brian's tzset changes have been
> pushed (see other discussion).
> 
> You can also find the test vectors online
> (https://github.com/jdoubleu/newlib-posix-tzset-tests/blob/main/timezones.h)
> and run the tests on linux with glibc
> (https://github.com/jdoubleu/newlib-posix-tzset-tests/tree/main/host_test).
> 
> Cheers
> ---
> 🙎🏻‍♂️ jdoubleu

> From 97fa4a760e67f4f553dbe18a3a75fa14e855916d Mon Sep 17 00:00:00 2001
> From: jdoubleu <hi@jdoubleu.de>
> Date: Thu, 7 Apr 2022 17:30:01 +0200
> Subject: [PATCH] add tests for tzset(3)
> 
> ---
>  newlib/testsuite/newlib.time/time.exp |  12 ++
>  newlib/testsuite/newlib.time/tzset.c  | 163 ++++++++++++++++++++++++++
>  2 files changed, 175 insertions(+)
>  create mode 100644 newlib/testsuite/newlib.time/time.exp
>  create mode 100644 newlib/testsuite/newlib.time/tzset.c

Hi,

I get the following failure on pru-none-elf and arm-none-eabi targets:

Assertion failed! Expected 1647906533 to equal 1647916532. winter time, timezone = "<+0123456789ABCDEF>3:33:33"
FAIL: newlib.time/tzset.c execution

Regards,
Dimitar

  parent reply	other threads:[~2022-04-10  8:43 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-07 15:58 jdoubleu
2022-04-08 21:21 ` Jeff Johnston
2022-04-10  8:43 ` Dimitar Dimitrov [this message]
2022-04-10 17:55   ` jdoubleu
2022-04-10 21:00     ` Dimitar Dimitrov
2022-04-11 11:17       ` jdoubleu
2022-04-11 17:27         ` Dimitar Dimitrov
2022-04-12 11:19           ` jdoubleu
2022-04-12 18:33             ` Brian Inglis
2022-04-07 23:34               ` [PATCH v2 0/2] add tzset/_r POSIX angle bracket <> support in TZ env var Brian Inglis
2022-04-07 23:34                 ` [PATCH v2 1/2] newlib/libc/time/tzset.c: doc update POSIX angle bracket <> support Brian Inglis
2022-04-07 23:34                 ` [PATCH v2 2/2] newlib/libc/time/tzset_r.c(_tzset_unlocked_r): " Brian Inglis
2022-04-08 19:11                 ` [PATCH v2 0/2] add tzset/_r POSIX angle bracket <> support in TZ env var Jeff Johnston
2022-04-13 17:53                 ` [PATCH] add tests for tzset(3) Brian Inglis
2022-04-13 20:33                   ` Jeff Johnston
2022-04-13 22:19                     ` Brian Inglis
2022-04-14  8:59                       ` jdoubleu
2022-04-14 16:31                         ` Brian Inglis
2022-04-14 19:23                           ` Jeff Johnston
2022-04-15 10:10                             ` jdoubleu
2022-04-27 19:30                               ` Jeff Johnston
2022-05-14 14:39                         ` jdoubleu
2022-05-16 16:05                           ` Dimitar Dimitrov
2022-05-16 17:38                             ` Jeff Johnston
2022-05-17  8:45                           ` [PATCH] update tzset tests jdoubleu
2022-05-18 18:48                             ` Dimitar Dimitrov
2022-05-18 20:56                               ` Keith Packard
2022-05-19  8:47                                 ` jdoubleu
2022-05-22  9:51                                   ` [PATCH v2] " jdoubleu
2022-05-22 21:02                                     ` Dimitar Dimitrov
2022-05-27 15:46                                       ` Jeff Johnston
2022-04-13 22:21               ` [PATCH] add tests for tzset(3) Brian Inglis
2022-04-29 15:46 Jeff Johnston
2022-05-12 18:35 ` jdoubleu
2022-05-16 17:49   ` Jeff Johnston

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YlKYmZ0oNLitMT2b@kendros \
    --to=dimitar@dinux.eu \
    --cc=hi@jdoubleu.de \
    --cc=newlib@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).