| Summary: | [2.6 M3 RC1] e2fsprogs ptest failed | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Manish Das <manish.das> |
| Component: | core | Assignee: | Changqing Li <changqing.li> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | anuj.mittal, meta.mr.watcher, meta.watcher, ross.burton |
| Version: | 2.6 | ||
| Target Milestone: | 2.6 M4 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Manish Das
2018-10-03 09:51:06 UTC
Happens because a missing quote in test script. Patch sent to list. With that fix and e2fsprogs-ptest in a core-image-minimal: root@bob:~# ptest-runner e2fsprogs START: ptest-runner 2018-10-04T11:23 BEGIN: /usr/lib/e2fsprogs/ptest sed: invalid option -- 'u' BusyBox v1.29.2 (2018-10-04 10:05:58 UTC) multi-call binary. (looks like we need to depend on sed, or patch out -u) debugfs 1.44.3 (10-July-2018) grep: ../lib/config.h: No such file or directory /usr/lib/e2fsprogs/ptest/test/f_detect_junk/script: line 3: [: : integer expression expected ([ error is because the file wasn't present) f_large_dir: 5000/65010 links, 16s @ 312/s f_large_dir: 10000/65010 links, 39s @ 128/s f_large_dir: 15000/65010 links, 61s @ 81/s f_large_dir: 20000/65010 links, 87s @ 57/s f_large_dir: 25000/65010 links, 109s @ 45/s f_large_dir: 30000/65010 links, 133s @ 37/s f_large_dir: 35000/65010 links, 152s @ 32/s f_large_dir: 40000/65010 links, 176s @ 28/s f_large_dir: 45000/65010 links, 200s @ 25/s f_large_dir: 50000/65010 links, 228s @ 21/s f_large_dir: 55000/65010 links, 251s @ 19/s f_large_dir: 60000/65010 links, 277s @ 18/s ERROR: Exit status is 9 TIMEOUT: /usr/lib/e2fsprogs/ptest The f_large_dir test takes so long, that ptest times out. I'm wondering if the e2fsprogs test is actually useful. Should we just remove it? |