Bug#1066962: wxwidgets3.2: 1 testsuite failed on loong64

2024-03-25 Thread zhangdandan

Hi,
   Thanks for your reply.
在 2024/3/22 上午10:45, Scott Talbert 写道:

On Sat, 16 Mar 2024 15:21:57 +0800 zhangdandan
 wrote:

Source: wxwidgets3.2
Version: 3.2.4+dfsg-3.1
Severity: serious
Tags: help
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

The following test failed on the loongarch64 architecture, compiled
20 hours ago (March 16th).

./uris/url.cpp:89: FAILED:
     REQUIRE( in_stream )
with expansion:
     0

==

test cases: 312 | 311 passed | 1 failed
assertions: 1230238 | 1230237 passed | 1 failed

make[1]: *** [debian/rules:89: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:22: binary-arch] Error 2
dpkg-buildpackage: error: debian/rules binary-arch subprocess

Hello,

This particular test is supposed to be skipped if the build host
doesn't have network connectivity.  Does the loong64 buildd have
network connectivity (unlike the other buildd's)?


Printed in_stream and found a NULL pointer.
Analyzing the test case again, I found that the buildds environment 
could not access http://detectportal.firefox.com/ and the text provided 
by the link is "success".
I've asked my Network Administrator to turn on access to 
http://detectportal.firefox.com.
I can currently ping the corresponding link in the buildd environment, 
as follows:

root@loong64-loongson-06:~# ping detectportal.firefox.com
PING prod.detectportal.prod.cloudops.mozgcp.net (34.107.221.82) 56(84) 
bytes of data.
64 bytes from 82.221.107.34.bc.googleusercontent.com (34.107.221.82): 
icmp_seq=1 ttl=52 time=150 ms
64 bytes from 82.221.107.34.bc.googleusercontent.com (34.107.221.82): 
icmp_seq=2 ttl=52 time=150 ms


- The result of the discussion in the previous email.
# python3 -m httpbin.core & export HTTPBIN_PID=$!; RC=0; cd tests && 
WX_TEST_WEBREQUEST_URL="http://localhost:5000; ./test ~[.] 
~[special-file] || RC=1; kill -9 ${HTTPBIN_PID}; exit $RC

All tests passed (1248603 assertions in 312 test cases)  //on loong64 ENV

- In addition, it is important to focus on the other test case.
# cd tests && wxUSE_XVFB=1 xvfb-run -a . /test_gui ~[.] ~WebView 
~wxDC::GetPartialTextExtent ~TextCtrlTestCase

Need to add loong64 support in d/rules, as follows:
```
diff --git a/debian/rules b/debian/rules
index 36f4770..1fb1451 100755
--- a/debian/rules
+++ b/debian/rules
@@ -9,7 +9,7 @@ TEST_GUI_FILTER = ~[.]
 ifneq (,$(filter $(DEB_HOST_ARCH), alpha loong64 mips64el riscv64 s390x))
 TEST_FILTER += ~[special-file]
 endif
-ifneq (,$(filter $(DEB_HOST_ARCH), alpha hppa mips64el ppc64 riscv64 
s390x sparc64 x32))
+ifneq (,$(filter $(DEB_HOST_ARCH), alpha hppa loong64 mips64el ppc64 
riscv64 s390x sparc64 x32))

 TEST_GUI_FILTER += ~WebView
 endif
 ifneq (,$(filter $(DEB_HOST_ARCH), i386))
```

Your suggestions are always welcome.
The wxwidgets3.2 itself blocks the compilation of 47 packages such as 
gnuplot.

And gnuplot blocks the compilation of 52 packages.
Please stay tuned for the build status of wxwidgets3.2 on loong64.
If you have any questions you can cantact me at any time.

Thanks,
Dandan Zhang



Bug#1066962: wxwidgets3.2: 1 testsuite failed on loong64

2024-03-21 Thread Scott Talbert
On Sat, 16 Mar 2024 15:21:57 +0800 zhangdandan
 wrote:
> Source: wxwidgets3.2
> Version: 3.2.4+dfsg-3.1
> Severity: serious
> Tags: help
> User: debian-loonga...@lists.debian.org
> Usertags: loong64
> 
> Dear maintainers,
> 
> The following test failed on the loongarch64 architecture, compiled
20 
> hours ago (March 16th).
> ```
> -
--
> URLTestCase
>    GetInputStream
> -
--
> ./uris/url.cpp:37
>
...

> 
> ./uris/url.cpp:89: FAILED:
>    REQUIRE( in_stream )
> with expansion:
>    0
> 
>
===

> test cases: 312 | 311 passed | 1 failed
> assertions: 1230238 | 1230237 passed | 1 failed
> 
> make[1]: *** [debian/rules:89: override_dh_auto_test] Error 1
> make[1]: Leaving directory '/<>'
> make: *** [debian/rules:22: binary-arch] Error 2
> dpkg-buildpackage: error: debian/rules binary-arch subprocess
returned 
> exit status 2
> ```
> The full build log can be found at 
>
https://buildd.debian.org/status/package.php?p=wxwidgets3.2=sid.
> 
> I have reproduced the above testsuite issues on my local loong64
rootfs 
> environment.
> After analyzing, I don't think this error has anything to do with 
> architecture.
> So please focus on this test case failure.
> 
> thanks,
> Dandan Zhang

Hello,

This particular test is supposed to be skipped if the build host
doesn't have network connectivity.  Does the loong64 buildd have
network connectivity (unlike the other buildd's)?

Unfortunately, there doesn't appear to be a loong64 porterbox, so I'm
unable to look into why this is failing.

Regards,
Scott 



Bug#1066962: wxwidgets3.2: 1 testsuite failed on loong64

2024-03-16 Thread zhangdandan

Source: wxwidgets3.2
Version: 3.2.4+dfsg-3.1
Severity: serious
Tags: help
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

The following test failed on the loongarch64 architecture, compiled 20 
hours ago (March 16th).

```
---
URLTestCase
  GetInputStream
---
./uris/url.cpp:37
...

./uris/url.cpp:89: FAILED:
  REQUIRE( in_stream )
with expansion:
  0

===
test cases: 312 | 311 passed | 1 failed
assertions: 1230238 | 1230237 passed | 1 failed

make[1]: *** [debian/rules:89: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:22: binary-arch] Error 2
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned 
exit status 2

```
The full build log can be found at 
https://buildd.debian.org/status/package.php?p=wxwidgets3.2=sid.


I have reproduced the above testsuite issues on my local loong64 rootfs 
environment.
After analyzing, I don't think this error has anything to do with 
architecture.

So please focus on this test case failure.

thanks,
Dandan Zhang