#I m seeing a weird thing maybe someone
brisk hound
It's all new the 2nd time
and then when it completes if I run the script again, it's all cached
and once or twice I had it randomly not need to rerun a second time
solid pagoda
Okay yeah it's almost certainly related to the fact that you are invoking the engine multiple times and making use of localdirs. I am a bit surprised by the inconsistency, but one possibility is that when you are writing to ./bin you may be changing your workdir, which will sometimes result in invalidation the next time around
It doesn't fully add up though
brisk hound
Yeah I clean the ./bin between script executions, so it should be consistent within the script run. But I'm happy to chalk it up to cross-engine weirdness and wait for the fancy new bash sdk 😄
solid pagoda
Yeah I clean the `./bin` between script executions, so it should be consistent w...
I suspect there probably has to be more than just cross-engine weirdness, but it's impossible to say what is that and what is potentially a different issue, so yeah I think for now we can only figure out more by having the fancy bash sdk and go from there
spare wraith
