Re: lib/57314: ATF unit tests fail on 3 of 7 cases in program lib/libc/c063/t_utimensat on evbarm/Rpi 02W

[Jim Spath <jspath55%gmail.com@localhost>]

The following reply was made to PR lib/57314; it has been noted by GNATS.

From: Jim Spath <jspath55%gmail.com@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: lib/57314: ATF unit tests fail on 3 of 7 cases in program
 lib/libc/c063/t_utimensat on evbarm/Rpi 02W
Date: Fri, 31 Mar 2023 10:24:44 -0400

 Michael - thank you for the reply. It sounds like this result might be
 expected though the underlying conditions may not be obvious.
 
 The /tmp filesystem is on the SD card for these systems. I followed
 these steps for the install:
 
 http://mail-index.netbsd.org/port-arm/2022/02/14/msg007592.html
 
 >  /tmp being a FAT filesystem or do you redirect the test to use a FAT fil=
 esystem?
 
 Not that I am aware. The "disk" layout looks like this:
 
 $ df -m /tmp
 Filesystem   1M-blocks      Used     Avail %Cap Mounted on
 /dev/ld0a        58604      5215     50458   9% /
 
 $ df -m
 Filesystem   1M-blocks      Used     Avail %Cap Mounted on
 /dev/ld0a        58604      5215     50458   9% /
 /dev/ld0e           79        73         5  92% /boot
 ptyfs                0         0         0 100% /dev/pts
 procfs               0         0         0 100% /proc
 tmpfs              112         0       111   0% /var/shm
 
 $ cat /etc/fstab
 # NetBSD /etc/fstab
 # See /usr/share/examples/fstab/ for more examples.
 ROOT.a          /               ffs     rw,noatime      1 1
 ROOT.e          /boot           msdos   rw      1 1
 ptyfs           /dev/pts        ptyfs   rw
 procfs          /proc           procfs  rw
 tmpfs           /var/shm        tmpfs   rw,-m1777,-sram%25
 
 # disklabel -r ld0
 # /dev/rld0:
 type: SCSI
 disk: STORAGE DEVICE
 label: fictitious
 flags: removable
 bytes/sector: 512
 sectors/track: 32
 tracks/cylinder: 64
 sectors/cylinder: 2048
 cylinders: 1217
 total sectors: 122167296
 rpm: 3600
 interleave: 1
 trackskew: 0
 cylinderskew: 0
 headswitch: 0           # microseconds
 track-to-track seek: 0  # microseconds
 drivedata: 0
 
 8 partitions:
 #        size    offset     fstype [fsize bsize cpg/sgs]
  a: 121970688    196608     4.2BSD      0     0     0  # (Cyl.     96 -  59=
 651)
  c: 122167296         0     unused      0     0        # (Cyl.      0 -  59=
 651)
  d: 122167296         0     unused      0     0        # (Cyl.      0 -  59=
 651)
  e:    163840     32768      MSDOS                     # (Cyl.     16 -    =
  95)
 
 dmesg shows:
 [     1.840447] ld0: 59652 MB, 7604 cyl, 255 head, 63 sec, 512
 bytes/sect x 122167296 sectors
 [     1.850447] ld0: 4-bit width, High-Speed/SDR25, 50.000 MHz
 
 I can try with TMPDIR set elsewhere, or other permutations that might
 shed light.
 
 Jim
 
 On Fri, Mar 31, 2023 at 4:35=E2=80=AFAM Michael van Elst <mlelstv@serpens.d=
 e> wrote:
 >
 > The following reply was made to PR lib/57314; it has been noted by GNATS.
 >
 > From: mlelstv%serpens.de@localhost (Michael van Elst)
 > To: gnats-bugs%netbsd.org@localhost
 > Cc:
 > Subject: Re: lib/57314: ATF unit tests fail on 3 of 7 cases in program li=
 b/libc/c063/t_utimensat on evbarm/Rpi 02W
 > Date: Fri, 31 Mar 2023 08:33:38 -0000 (UTC)
 >
 >  jspath55%gmail.com@localhost writes:
 >
 >  >tc-end: 1679971113.937139, utimensat_fd, failed, /usr/src/tests/lib/lib=
 c/c063/t_utimensat.c:78: st.st_atimespec.tv_sec =3D=3D tptr[0].tv_sec not m=
 et
 >
 >  >The failing systems run on microSD media, while other systems are on SS=
 D or USB storage.
 >
 >
 >  These errors occur if the filesystem used for testing cannot handle
 >  timestamps with even 1-second resolution, e.g.: msdosfs.
 >
 >  Do you run the test with /tmp being a FAT filesystem or do you
 >  redirect the test to use a FAT filesystem?
 >