control@bugs.debian.org Bcc: Subject: Re: Bug#932927 closed by xiao sheng wen(肖盛文) <atzlinux@sina.com> (fixed in 4.1.1-5) Reply-To: In-Reply-To: <[🔎] 0e8fef28-132d-da7b-3047-82648381d639@sina.com> user debian-riscv@lists.debian.org usertag 932927 - riscv64 thanks On 2022-06-18 15:53, xiao sheng wen(肖盛文) wrote: > Hi Aurelien, > > > 在 2022/6/18 12:39, Aurelien Jarno 写道: > > control: reopen 932927 > > control: found 932927 4.1.1-5 > > > > On 2022-06-17 08:33, Debian Bug Tracking System wrote: > > > > #932927: libotr: buggy unit test: test_auth.c: test_auth_clear() > > > > It has been closed by xiao sheng wen(肖盛文) <atzlinux@sina.com>. > > > > -- > > 932927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932927 > > > > > From: "xiao sheng wen(肖盛文)" <atzlinux@sina.com> > > > To: 932927@bugs.debian.org, 932927-done@bugs.debian.org > > > > > > control: fixed -1 4.1.1-5 > > > > > > > > > tests/unit$ ./test_auth is run OK now: > > > > > > > > > ./run.sh test_list > > > unit/test_auth ................................. ok > > > > > > > > > atzlinux@Debian-StarFive:~/libotr/tests/unit$ ./test_auth > > > 1..5 > > > ok 1 - OTR auth info init is valid > > > ok 2 - OTR auth info clear is valid > > > ok 3 - OTR auth start v23 is valid > > > ok 4 - Copy not done > > > ok 5 - Copy OK > > > > > I confirm that the problem is not visible anymore on riscv64, probably > > due to the switch from gcc 8 to 10. > > > > However the underlying bug is still there and might appear again with a > > toolchain change, on riscv64 or another architecture. I am therefore > > reopening the bug. > > > > Regards > > Aurelien > > There is a possible is that the underlying bug perhaps had already fixed in the some new version of one package. > > Do this bug need to riscv porter team pay close attention to it? No this bug can be ignored from the riscv point of view (unless it reappears at some point ;-) > I'm reviewing the bug list that has riscv64 tag: > > https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=debian-riscv%40lists.debian.org&tag=riscv64 In that case the best is to keep the bug open, but remove it from that user bug list. That should be done with that mail. Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurelien@aurel32.net http://www.aurel32.net
Attachment:
signature.asc
Description: PGP signature