Tomasz Dziendzielski 8b792d4f75 bitbake: event: Prevent bitbake from executing event handler for wrong multiconfig target ...

When multiconfig is used bitbake might try to run events that don't
exist for specific mc target. In cooker.py we pass
`self.databuilder.mcdata[mc]` data that contains names of events'
handlers per mc target, but fire_class_handlers uses global _handlers
variable that is created during parsing of all the targets.

This leads to a problem where bitbake runs event handler that don't
exist for a target or even overrides them - if multiple targets use
event handler with the same name but different code then only one
version will be executed for all targets.

See [YOCTO #13071] for detailed bug information.

Add mc target name as a prefix to event handler name so there won't be
two different handlers with the same name. Add internal __BBHANDLERS_MC
variable to have the handlers lists per machine.

(Bitbake rev: 5f7fdf7b2d8c59805c8ef4dae84f536baa5e172b)

Signed-off-by: Tomasz Dziendzielski <tomasz.dziendzielski@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

2021-02-16 11:26:11 +00:00

..

parse_py

bitbake: logging: Make bitbake logger compatible with python logger

2021-02-10 23:48:16 +00:00

__init__.py

bitbake: logging: Make bitbake logger compatible with python logger

2021-02-10 23:48:16 +00:00

ast.py

bitbake: event: Prevent bitbake from executing event handler for wrong multiconfig target

2021-02-16 11:26:11 +00:00