---
About the issue of 'bitbake meta-oe-ptest-image-mariadb -ctestimage', I have no
idea yet and will do more investigation.
Please let me know if you have any suggestions, thanks!
> -Original Message-
> From: Khem Raj
> Sent: Friday,
it also needs perl-module-test-more rdep for
FAIL: dbug
tests to pass.
There still remains one failure on musl
70/70 Testing: test-connect
70/70 Test: test-connect
Command: "/usr/lib/mariadb/ptest/unittest/embedded/test-connect-t"
Directory: /usr/lib/mariadb/ptest/unittest/embedded
"test-connec
When running manually, I see this
root@qemux86-64:/usr/lib/mariadb/ptest# ./run-ptest
sed: unrecognized option: u
BusyBox v1.36.1 () multi-call binary.
Usage: sed [-i[SFX]] [-nrE] [-f FILE]... [-e CMD]... [FILE]...
or: sed [-i[SFX]] [-nrE] CMD [FILE]...
So I guess it needs a full sed command. Ad
while running
bitbake meta-oe-ptest-image-mariadb -ctestimage
I am seeing
WARNING: meta-oe-ptest-image-mariadb-1.0-r0 do_testimage: There were
failing ptests.
Traceback (most recent call last):
File
"/mnt/b/yoe/master/sources/poky/meta/lib/oeqa/core/decorator/__init__.py",
line 35, in wrapped
70 test cases in all, and all of them are PASS.
There are some specific steps before doing test,
please refer to the comments in run-ptest.
Test results:
root@intel-x86-64:~# ptest-runner mariadb
START: ptest-runner
2023-09-14T15:17
BEGIN: /usr/lib64/mariadb/ptest
PASS: strings
PASS: json
PASS: si
