| Summary: | [Yocto-2.6_M1.RC1] Crosstap doesn't work on 2.6 M1 RC1 | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Meta-yocto | Reporter: | pankaj yadav <pankaj-y> |
| Component: | meta-yocto | Assignee: | Manish Das <manish.das> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | manish.das, poky.bs.watcher, poky.watcher |
| Version: | 2.6 | ||
| Target Milestone: | 2.7 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
pankaj yadav
2018-06-20 10:16:14 UTC
While Regression, I am unable to see this issue with below mentioned cofiguration : Branch: master Build name: yocto-2.5_M1.rc1 poky commit: b73e96e7f3f5d1ba3a221d99792a7a3c7ef42c21 Architecture : x86-64 Does the test work other than showing a WARNING or are there other issues as well? With 2.6_M1.RC1 : I don't see "crosstap" has related output on host machine with WARNING message. With 2.5_M1.RC1 (regression with previous build): I see "crosstap" has related output on host machine but with WARNING message. The question appears to have been answered, if not put it back into NEEDINFO. Regression with 2.5_M4.RC1 : I don't see "crosstap" has related output on host machine with WARNING message. I am able to see this issue with below mentioned configuration : Build name: yocto-2.6M2.rc1 poky commit: b0f2f690a3513e4c9fa30fee1b8d7ac2d7140657 Architecture : x86-64 It seems it is another instance of non-bug also reported as [YOCTO #12974] https://bugzilla.yoctoproject.org/show_bug.cgi?id=12974. In short it seems that some output was expected from SystemTap script but since nothing in the system uses 'open' system call none of output was produced. Please look at 'Comment 2 of YOCTO #12974' https://bugzilla.yoctoproject.org/show_bug.cgi?id=12974#c2 for more details. Please note I am guessing that trace_open.stp script has the same content as it was reported in [YOCTO #12974]. To be 100% sure it is the case I put this PR in NEEDINFO state. Upon response if it is the same trace_open.stp script please consider putting this PR into RESOLVED state INVALID resolution based on the same rational as it was explained in [YOCTO #12974] |