>I did also wonder if we should be changing each of the event register >callers, or doing something inside the event register function instead? That should be possible. I'll work on that. Thanks and sorry for the problem. Best regards, Tomasz Dziendzielski wt., 9 lut 2021 o 16:50 Richard Purdie napisaƂ(a): > On Sun, 2021-02-07 at 12:46 +0100, Tomasz Dziendzielski wrote: > > 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. > > > > Signed-off-by: Tomasz Dziendzielski > > > > --- v4 add mc prefix to _bb_diskmonitor event handler to fix build, both > build and test_stoptask_behavior should be working now > > --- > > lib/bb/cookerdata.py | 5 ++++- > > lib/bb/event.py | 2 ++ > > lib/bb/parse/ast.py | 7 ++++++- > > lib/bb/runqueue.py | 15 +++++++++++++-- > > 4 files changed, 25 insertions(+), 4 deletions(-) > > This still isn't right I'm afraid: > > https://autobuilder.yoctoproject.org/typhoon/#/builders/39/builds/3057 > > I did also wonder if we should be changing each of the event register > callers, or doing something inside the event register function instead? > > Cheers, > > Richard > >