https://buildd.debian.org/status/logs.php?pkg=gcc-12&arch=mips64el

...
Finished
--------

I: Built successfully
chmod: cannot access '/<<PKGBUILDDIR>>/build/mips64el-linux-gnuabi64/libstdc++-v3/testsuite/normal3/filesystem-test.FSLTZS-last_write_time': Value too large for defined data type
chmod: cannot access '/<<PKGBUILDDIR>>/build/mips64el-linux-gnuabi64/libstdc++-v3/testsuite/normal2/filesystem-test.5zDnmX-last_write_time': Value too large for defined data type
E: Can't chmod /<<BUILDDIR>> to g+w:
E: chmod g+w /<<BUILDDIR>> failed.
du: cannot access '/<<PKGBUILDDIR>>/build/mips64el-linux-gnuabi64/libstdc++-v3/testsuite/normal3/filesystem-test.FSLTZS-last_write_time': Value too large for defined data type
du: cannot access '/<<PKGBUILDDIR>>/build/mips64el-linux-gnuabi64/libstdc++-v3/testsuite/normal2/filesystem-test.5zDnmX-last_write_time': Value too large for defined data type
E: read_command failed to execute du
E: Cannot determine space needed for /<<PKGBUILDDIR>> (du failed)
...


This is apparently mips64el-only (no problem on mipsel),
and it is not obvious how to reproduce it on the porterbox.

The timing when the issue started matches when coreutils 9.1-1
started being in the chroot (but the problem might be elsewhere).

Any clues what might be going wrong?

Thanks
Adrian

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Adrian Bunk <bunk@debian.org> 于2022年10月25日周二 21:50写道：

https://buildd.debian.org/status/logs.php?pkg=gcc-12&arch=mips64el

...
Finished
--------

I: Built successfully
chmod: cannot access '/<<PKGBUILDDIR>>/build/mips64el-linux-gnuabi64/libstdc++-v3/testsuite/normal3/filesystem-test.FSLTZS-last_write_time': Value too large for defined data type
chmod: cannot access '/<<PKGBUILDDIR>>/build/mips64el-linux-gnuabi64/libstdc++-v3/testsuite/normal2/filesystem-test.5zDnmX-last_write_time': Value too large for defined data type
E: Can't chmod /<<BUILDDIR>> to g+w:
E: chmod g+w /<<BUILDDIR>> failed.
du: cannot access '/<<PKGBUILDDIR>>/build/mips64el-linux-gnuabi64/libstdc++-v3/testsuite/normal3/filesystem-test.FSLTZS-last_write_time': Value too large for defined data type
du: cannot access '/<<PKGBUILDDIR>>/build/mips64el-linux-gnuabi64/libstdc++-v3/testsuite/normal2/filesystem-test.5zDnmX-last_write_time': Value too large for defined data type
E: read_command failed to execute du
E: Cannot determine space needed for /<<PKGBUILDDIR>> (du failed)
...

This is apparently mips64el-only (no problem on mipsel),
and it is not obvious how to reproduce it on the porterbox.

The timing when the issue started matches when coreutils 9.1-1
started being in the chroot (but the problem might be elsewhere).

Any clues what might be going wrong?

I am trying to reproduce it on my local machines.

Thanks
Adrian

--
YunQiang Su

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

YunQiang Su <wzssyqa@gmail.com> 于2022年10月26日周三 01:56写道：

Adrian Bunk <bunk@debian.org> 于2022年10月25日周二 21:50写道：

https://buildd.debian.org/status/logs.php?pkg=gcc-12&arch=mips64el

...
Finished
--------

I: Built successfully
chmod: cannot access '/<<PKGBUILDDIR>>/build/mips64el-linux-gnuabi64/libstdc++-v3/testsuite/normal3/filesystem-test.FSLTZS-last_write_time': Value too large for defined data type
chmod: cannot access '/<<PKGBUILDDIR>>/build/mips64el-linux-gnuabi64/libstdc++-v3/testsuite/normal2/filesystem-test.5zDnmX-last_write_time': Value too large for defined data type

I cannot reproduce this problem on my local machines.
Can you help to try to reproduce this problem on buildd nodes?

E: Can't chmod /<<BUILDDIR>> to g+w:
E: chmod g+w /<<BUILDDIR>> failed.
du: cannot access '/<<PKGBUILDDIR>>/build/mips64el-linux-gnuabi64/libstdc++-v3/testsuite/normal3/filesystem-test.FSLTZS-last_write_time': Value too large for defined data type
du: cannot access '/<<PKGBUILDDIR>>/build/mips64el-linux-gnuabi64/libstdc++-v3/testsuite/normal2/filesystem-test.5zDnmX-last_write_time': Value too large for defined data type
E: read_command failed to execute du
E: Cannot determine space needed for /<<PKGBUILDDIR>> (du failed)
...

This is apparently mips64el-only (no problem on mipsel),
and it is not obvious how to reproduce it on the porterbox.

The timing when the issue started matches when coreutils 9.1-1
started being in the chroot (but the problem might be elsewhere).

Any clues what might be going wrong?

I am trying to reproduce it on my local machines.

Thanks
Adrian

--
YunQiang Su

--
YunQiang Su

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Thu, Oct 27, 2022 at 07:50:17PM +0800, YunQiang Su wrote:

YunQiang Su <wzssyqa@gmail.com> 于2022年10月26日周三 01:56写道：

Adrian Bunk <bunk@debian.org> 于2022年10月25日周二 21:50写道：

https://buildd.debian.org/status/logs.php?pkg=gcc-12&arch=mips64el

...
Finished
--------

I: Built successfully
chmod: cannot access '/<<PKGBUILDDIR>>/build/mips64el-linux-gnuabi64/libstdc++-v3/testsuite/normal3/filesystem-test.FSLTZS-last_write_time': Value too large for defined data type
chmod: cannot access '/<<PKGBUILDDIR>>/build/mips64el-linux-gnuabi64/libstdc++-v3/testsuite/normal2/filesystem-test.5zDnmX-last_write_time': Value too large for defined data type

I cannot reproduce this problem on my local machines.
Can you help to try to reproduce this problem on buildd nodes?
...

Not from me, if I had a way to reproduce I would have debugged further
from that.

YunQiang Su

cu
Adrian

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi,

On 2022-10-28 08:59, Adrian Bunk wrote:

On Thu, Oct 27, 2022 at 07:50:17PM +0800, YunQiang Su wrote:

YunQiang Su <wzssyqa@gmail.com> 于2022年10月26日周三 01:56写道：

Adrian Bunk <bunk@debian.org> 于2022年10月25日周二 21:50写道：

https://buildd.debian.org/status/logs.php?pkg=gcc-12&arch=mips64el

...
Finished
--------

I: Built successfully
chmod: cannot access '/<<PKGBUILDDIR>>/build/mips64el-linux-gnuabi64/libstdc++-v3/testsuite/normal3/filesystem-test.FSLTZS-last_write_time': Value too large for defined data type
chmod: cannot access '/<<PKGBUILDDIR>>/build/mips64el-linux-gnuabi64/libstdc++-v3/testsuite/normal2/filesystem-test.5zDnmX-last_write_time': Value too large for defined data type

I cannot reproduce this problem on my local machines.
Can you help to try to reproduce this problem on buildd nodes?
...

Not from me, if I had a way to reproduce I would have debugged further
from that.

I have been able to reproduce by building gcc-12 on the eller.d.o
porterbox. It can be reduced to this simple test:

(sid_mips64el-dchroot)aurel32@eller:~$ touch -d 20390101 t (sid_mips64el-dchroot)aurel32@eller:~$ chmod +x t
chmod: cannot access 't': Value too large for defined data type (sid_mips64el-dchroot)aurel32@eller:~$

It seems related to the y2038 support in either coreutils or glibc.

Regards
Aurelien

--
Aurelien Jarno GPG: 4096R/1DDD8C9B aurelien@aurel32.net http://www.aurel32.net

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Fri, Oct 28, 2022 at 2:05 PM Aurelien Jarno <aurelien@aurel32.net> wrote:

On 2022-10-28 08:59, Adrian Bunk wrote:

On Thu, Oct 27, 2022 at 07:50:17PM +0800, YunQiang Su wrote:

YunQiang Su <wzssyqa@gmail.com> 于2022年10月26日周三 01:56写道：

Adrian Bunk <bunk@debian.org> 于2022年10月25日周二 21:50写道：

https://buildd.debian.org/status/logs.php?pkg=gcc-12&arch=mips64el

...
Finished
--------

I: Built successfully
chmod: cannot access '/<<PKGBUILDDIR>>/build/mips64el-linux-gnuabi64/libstdc++-v3/testsuite/normal3/filesystem-test.FSLTZS-last_write_time': Value too large for defined data type
chmod: cannot access '/<<PKGBUILDDIR>>/build/mips64el-linux-gnuabi64/libstdc++-v3/testsuite/normal2/filesystem-test.5zDnmX-last_write_time': Value too large for defined data type

I cannot reproduce this problem on my local machines.
Can you help to try to reproduce this problem on buildd nodes?
...

Not from me, if I had a way to reproduce I would have debugged further
from that.

I have been able to reproduce by building gcc-12 on the eller.d.o
porterbox. It can be reduced to this simple test:

(sid_mips64el-dchroot)aurel32@eller:~$ touch -d 20390101 t (sid_mips64el-dchroot)aurel32@eller:~$ chmod +x t
chmod: cannot access 't': Value too large for defined data type (sid_mips64el-dchroot)aurel32@eller:~$

It seems related to the y2038 support in either coreutils or glibc.

There's a thread going on over at debian-arm that might provide some
insight: https://lists.debian.org/debian-arm/2022/10/msg00020.html . I
don't think it will be helpful to fix this problem, however.

Jeff

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi,

On 2022-10-28 20:04, Aurelien Jarno wrote:

Hi,

On 2022-10-28 08:59, Adrian Bunk wrote:

On Thu, Oct 27, 2022 at 07:50:17PM +0800, YunQiang Su wrote:

YunQiang Su <wzssyqa@gmail.com> 于2022年10月26日周三 01:56写道：

Adrian Bunk <bunk@debian.org> 于2022年10月25日周二 21:50写道：

https://buildd.debian.org/status/logs.php?pkg=gcc-12&arch=mips64el

...
Finished
--------

I: Built successfully
chmod: cannot access '/<<PKGBUILDDIR>>/build/mips64el-linux-gnuabi64/libstdc++-v3/testsuite/normal3/filesystem-test.FSLTZS-last_write_time': Value too large for defined data type
chmod: cannot access '/<<PKGBUILDDIR>>/build/mips64el-linux-gnuabi64/libstdc++-v3/testsuite/normal2/filesystem-test.5zDnmX-last_write_time': Value too large for defined data type

I cannot reproduce this problem on my local machines.
Can you help to try to reproduce this problem on buildd nodes?
...

Not from me, if I had a way to reproduce I would have debugged further from that.

I have been able to reproduce by building gcc-12 on the eller.d.o
porterbox. It can be reduced to this simple test:

(sid_mips64el-dchroot)aurel32@eller:~$ touch -d 20390101 t (sid_mips64el-dchroot)aurel32@eller:~$ chmod +x t
chmod: cannot access 't': Value too large for defined data type (sid_mips64el-dchroot)aurel32@eller:~$

It seems related to the y2038 support in either coreutils or glibc.

This is a glibc issue introduced in 2.35, that has been triggered by the
new coreutils version. I have opened #1022991 to track the issue.

Regards,
Aurelien

--
Aurelien Jarno GPG: 4096R/1DDD8C9B aurelien@aurel32.net http://www.aurel32.net

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)