openresty / openresty/lua-resty-core
Random test failures in t/re-gmatch.t
Open
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 853
- Forks
- 286
- Avg merge
- 35m
- Merged PRs (30d)
- 1
Description
I'm seeing the following random test failures on ubuntu:trusty x86_64:
$ TEST_NGINX_RANDOMIZE=1 \
prove -r -j2 -I../test-nginx/lib \
t/stream/re-gmatch.t
t/stream/re-gmatch.t .. 1/?
# Failed test 'TEST 2: matched, no submatch, jit compile, regex cache - pattern "(?^:\[TRACE\s+\d+ content_by_lua\(nginx\.conf:\d+\):4 loop\])" should match a line in error.log (req 0)'
# at /home/dev/work/org/lua-resty-core/../test-nginx/lib/Test/Nginx/Socket.pm line 1213.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with t/stream/re-gmatch.t and reproduce the failure using TEST_NGINX_RANDOMIZE=1 with the provided prove command. Inspect the failure reported at Test/Nginx/Socket.pm line 1213. Done means the randomized test no longer fails on the stated Ubuntu Trusty x86_64 environment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100