Bug 12215

Summary: ptest-runner libpcre one failed
Product: [QA/Testing] Build Testing Reporter: oscar lopez arandas <oscarx.lopez.arandas>
Component: generalAssignee: Juro Bystricky <juro.bystricky>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium CC: juro.bystricky
Version: 2.4   
Target Milestone: 2.5   
Hardware: NUC   
OS: x86_64   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know
Attachments:
Description Flags
full_log none

Description oscar lopez arandas 2017-10-10 21:38:20 UTC 
Created attachment 4072 [details]
full_log

tests were executed and The pass rate goes back the percentage, observing 1 failures on the  libpcre 

POKY : 2.4_M4_r2 COMMIT:da05a01423a60a23cd1073eb0ad3776e5bf4f2a8
HW: NUC  6i5SYH 
IMAGES:
https://autobuilder.yocto.io/pub/releases/yocto-2.4.rc2/machines/genericx86-64/core-image-sato-sdk-ptest-genericx86-64.hddimg

Results  Chart table:
https://wiki.yoctoproject.org/wiki/Ptest_da05a01423a60a23cd1073eb0ad3776e5bf4f2a8

STEPS: automatic
 1. Download pTest image from autobuilder( you can find core-image-sato-sdk image in pTest directory)

* we test it on NUC with genericx86-64
2. Install the image on DUT (using legacy boot)
3) Configure the network so it be able to work externally:
- Export the proxy using "export http_proxy=<add your proxy link>" command eg

And check if you have internet connection, typing on terminal:
$ wget www.google.com
4. In command line type
$ ptest-runner > ptest.log 

EXPECTED OUTCOME:
The pass rate goes up the percentage


ACTUAL OUTCOME:
The pass rate goes back the percentage
==========================================
BEGIN: /usr/lib/libpcre/ptest
make[1]: Entering directory '/usr/lib/libpcre/ptest'
PASS: pcre_stringpiece_unittest
FAIL: RunTest
PASS: RunGrepTest
=============================================
full log in attachment
Comment 1 Juro Bystricky 2017-10-12 01:09:32 UTC 
This is one of those tests that logs results locally. If you look into /usr/lib/libpcre/ptest , all three individual test results are in separate log files.
The failing one (RunTest.log) says:

...
Test 3: Locale-specific features (using fr_FR locale)
...
This may mean there is a problem with the locale settings rather than a bug on PCRE.
Comment 2 Juro Bystricky 2017-10-12 20:38:16 UTC 
So because there is now locale fr_FR present, the locale gets tested and the test fails. The locale was not present before, so this is a new test.

It is not quite clear why the test fails, the testing is done by the program "pcretest". Looking at the source code (pcretest.c) I see this will not be a walk in the park, as the this is basically just one giant spaghetti code. (the "test routine" is 2783 lines long!)
Comment 3 Juro Bystricky 2018-03-29 14:50:24 UTC 
https://patchwork.openembedded.org/patch/149701/