Turbo cache

Added creation of the functor cache for the Turbo production. Related to LBOPG-47

@sbenson Can you check that I added the right option files? For some reason I did not manage to access the files from AppConfig.

Also some dst files ended up in the build directory. Is this is a problem or do we have an option to switch off the output creation?

Marked this merge request as a Work In Progress

Nightlies are failing because they cannot import Tesla. Locally it does not work because TurboStreamProd is unknown.

@sstahl, your options look good to me.

By the way, which Nightlies are failing. I looked today and I don't see any related to not being able to import Tesla.

For the TurboStreamProd thing, could this be because it is a DBASE package so doesnt get pulled in when you ask that Tesla is included?

The build of DaVinci shows an error ( lhcb-head slot ). The tests are not affected.

I am guessing that TurboCache not being in DaVinciSys is a problem.

Added 2 commits:

• 89bb6dab - Add missing entry in DaVinciSys
• c101a27b - Update cmt requirements file

Good catch.

Unmarked this merge request as a Work In Progress

Added 1 commit:

• 40d3ab65 - Workaround for the TurboCache compilation

I couldn't find the real issue, but replaced

from Configurables import Tesla

with

from Tesla.Configuration import Tesla

which should work tomorrow. The first way of doing things relies on a database of configurables being generated before the cache (which it is!), but somehow something is wrong.

By the way, in Moore we have exactly the same workaround. This pattern from Configurables import X seems like a bad idea anyway.

Thanks! Interesting... the StrippingCache uses only AppMgr and not DaVinci.

Now it does not know about TurboStreamProd. Is there a way to let it know about it?

Looks like it finds it at /afs/cern.ch/lhcb/software/DEV/nightlies/DBASE/TurboStreamProd/v99r99, which is not up to date with the released version /afs/cern.ch/lhcb/software/releases/DBASE/TurboStreamProd/v4r1p4/ @bcouturi, can you have a look?

Any news on this front?

It still misses TurboStreamProd. @bcouturi can you check why TurboStreamProd points to the wrong version?

Looks like that one just wasn't updated. Need to discuss with Marco to sort it once and for all...

Hello @bcouturi, @sstahl, do keep me posted on this so that this pending MR can also be dealt with/close. Thanks.

A new software stack is being finalised and I still do not know whether I should accept and include this MR ... It's been around for a while now ... Please let me know asap.