| Summary: | methodpool does not account for two identically named files (different paths) that provide the different methods | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BitBake | Reporter: | Mark Hatle <mark.hatle> |
| Component: | bitbake | Assignee: | Richard Purdie <richard.purdie> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | jessica.zhang, poky.bs.watcher, poky.watcher |
| Version: | unspecified | ||
| Target Milestone: | 1.5 M1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Mark Hatle
2013-05-07 22:28:03 UTC
The issue is that PythonMethodNode in ast.py uses self.modulename as a unique identifier for the insertion of the new method. If you have two identically named files, this breaks since one is parsed and the other is not. The issue is complicated by the issue only occurring if both files are parsed by the same process. In separate processes you don't see the conflict. Patches on bitbake mailing list to resolve this. Fixed in master with http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=8bef99d3c85f48ff409eaebb964b1c45b203bdcf (there is cleanup in the following patches) |