Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Error running the tests on ppc64le

Open
  • Is something wrong?
#91 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
c, linux
Domain
operating-systems, testing-qa

Research direction

Start by rerunning prove -r t/ on the ppc64le environment and inspect the failures in t/location-async.t, t/location.t, t/subrequest-async.t, t/subrequest.t, and t/unused.t alongside t/servroot/logs/error.log. Determine the cause of the missing expected log lines and make the affected tests pass without regressing the other tests.

Written by the indexing model from the issue text.

Description

Any pointers/help on how to fix the failed tests.

Error log:-
[root@pts00450-vm1 echo-nginx-module-0.61]# cat t/servroot/logs/error.log
2019/09/27 17:36:34 [notice] 29395#0: using the "epoll" event method
2019/09/27 17:36:34 [notice] 29395#0: openresty/1.17.1.1rc0
2019/09/27 17:36:34 [notice] 29395#0: built by gcc 4.8.5 20150623 (Red Hat 4.8.5-39) (GCC)
2019/09/27 17:36:34 [notice] 29395#0: OS: Linux 3.10.0-957.27.2.el7.ppc64le
2019/09/27 17:36:34 [notice] 29395#0: getrlimit(RLIMIT_NOFILE): 1024:4096
2019/09/27 17:36:35 [notice] 29396#0: signal 15 (SIGTERM) received from 29389, exiting
2019/09/27 17:36:35 [notice] 29396#0: signal 3 (SIGQUIT) received from 29389, shutting down
2019/09/27 17:36:35 [info] 29396#0: epoll_wait() failed (4: Interrupted system call)
2019/09/27 17:36:35 [notice] 29396#0: exiting
2019/09/27 17:36:35 [notice] 29396#0: exit

[root@pts00450-vm1 echo-nginx-module-0.61]# nginx -v
nginx version: openresty/1.17.1.1rc0
[root@pts00450-vm1 echo-nginx-module-0.61]#

Detailed error:
[root@pts00450-vm1 echo-nginx-module-0.61]# prove -r t/
t/abort-parent.t ...... skipped: not working at all
t/blocking-sleep.t .... ok
t/echo-after-body.t ... ok
t/echo-before-body.t .. ok
t/echo-duplicate.t .... ok
t/echo-timer.t ........ ok
t/echo.t .............. ok
t/exec.t .............. ok
t/filter-used.t ....... ok
t/foreach-split.t ..... ok
t/gzip.t .............. ok
t/if.t ................ ok
t/incr.t .............. ok
t/location-async.t .... 33/90
Failed test 'TEST 16: unsafe uri - pattern "echo_location_async sees unsafe uri: "/../foo"" should match a line in error.log (req 0)'
at /usr/local/share/perl5/Test/Nginx/Socket.pm line 1213.

Failed test 'TEST 16: unsafe uri - pattern "echo_location_async sees unsafe uri: "/../foo"" should match a line in error.log (req 1)'
at /usr/local/share/perl5/Test/Nginx/Socket.pm line 1213.
t/location-async.t .... 79/90 # Looks like you failed 2 tests of 90.
t/location-async.t .... Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/90 subtests
t/location.t .......... 53/96
Failed test 'TEST 14: unsafe uri - pattern "echo_location sees unsafe uri: "/../foo"" should match a line in error.log (req 0)'
at /usr/local/share/perl5/Test/Nginx/Socket.pm line 1213.

Failed test 'TEST 14: unsafe uri - pattern "echo_location sees unsafe uri: "/../foo"" should match a line in error.log (req 1)'
at /usr/local/share/perl5/Test/Nginx/Socket.pm line 1213.
t/location.t .......... 75/96 # Looks like you failed 2 tests of 96.
t/location.t .......... Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/96 subtests
t/mixed.t ............. ok
t/request-body.t ...... ok
t/request-info.t ...... ok
t/sleep.t ............. ok
t/status.t ............ ok
t/subrequest-async.t .. 5/118
Failed test 'TEST 20: unsafe uri - pattern "echo_subrequest_async sees unsafe uri: "/../foo"" should match a line in error.log (req 0)'
at /usr/local/share/perl5/Test/Nginx/Socket.pm line 1213.
t/subrequest-async.t .. 28/118
Failed test 'TEST 20: unsafe uri - pattern "echo_subrequest_async sees unsafe uri: "/../foo"" should match a line in error.log (req 1)'
at /usr/local/share/perl5/Test/Nginx/Socket.pm line 1213.
t/subrequest-async.t .. 99/118 # Looks like you failed 2 tests of 118.
t/subrequest-async.t .. Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/118 subtests
t/subrequest.t ........ 113/130
Failed test 'TEST 19: unsafe uri - pattern "echo_subrequest sees unsafe uri: "/../foo"" should match a line in error.log (req 0)'
at /usr/local/share/perl5/Test/Nginx/Socket.pm line 1213.

Failed test 'TEST 19: unsafe uri - pattern "echo_subrequest sees unsafe uri: "/../foo"" should match a line in error.log (req 1)'
at /usr/local/share/perl5/Test/Nginx/Socket.pm line 1213.
Looks like you failed 2 tests of 130.
t/subrequest.t ........ Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/130 subtests
t/unused.t ............ 1/20
Failed test 'TEST 1: filters used - pattern "echo header filter, uri "/echo?blah"" should match a line in error.log (req 0)'
at /usr/local/share/perl5/Test/Nginx/Socket.pm line 1213.

Failed test 'TEST 1: filters used - pattern "echo body filter, uri "/echo?blah"" should match a line in error.log (req 0)'
at /usr/local/share/perl5/Test/Nginx/Socket.pm line 1213.

Failed test 'TEST 1: filters used - pattern "echo header filter, uri "/echo?blah"" should match a line in error.log (req 1)'
at /usr/local/share/perl5/Test/Nginx/Socket.pm line 1213.

Failed test 'TEST 1: filters used - pattern "echo body filter, uri "/echo?blah"" should match a line in error.log (req 1)'
at /usr/local/share/perl5/Test/Nginx/Socket.pm line 1213.
t/unused.t ............ 11/20 # Looks like you failed 4 tests of 20.
t/unused.t ............ Dubious, test returned 4 (wstat 1024, 0x400)
Failed 4/20 subtests

Dominant language
C
Stars
1.2k
Forks
250
Avg merge
25m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openresty/echo-nginx-module

All issues in openresty/echo-nginx-module

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.