Using the sstate-plaindir flag to specify that a single directory should be saved to sstate can race with other tasks if they are attempting to read a file from that directory. This occurs because the sstate code renames the directory to a temporary location to create the sstate object, then renames it back when it is finished, meaning there is a period of time where the directory doesn't exist.
Example: https://autobuilder.yoctoproject.org/typhoon/#/builders/56/builds/680
http://lists.openembedded.org/pipermail/openembedded-core/2019-September/286979.html
f5259a62d444dfc221a9ba592dbca35564f794ac ac27d12fe5480e9b8cc93de6a32bf9631c52d7f4