I bumped into a weird entity cache invalidation issue in one of my module's test.
After my test updates a user it seems the user storage does not get invalidated automatically - only in tests, I could not reproduce this problem by executing the same actions in the UI. I think this problem is a side-effect of \Drupal::service() vs. $this->container usage in tests.
When I saw my test had started to fail then I automatically added $this->container->get('entity_type.manager')->getStorage('user')->resetCache(); call to my test to ensure user cache is empty before my test loads the user with user_load_by_mail(). Even after this forced cache clear my test still failed so I started to go deeper in code and then I realized the memory cache inside $this->container->get('entity_type.manager')->getStorage('user) is not the same as in \Drupal::service('entity_type.manager')->getStorage('user') . So basically I cleared an already empty memory cache and user_load_by_email() used a completely different storage/memory cache which has not been cleared yet.
I think when a user entity gets updated Drupal automatically invalidates the related cache entries, but what if in tests it runs the invalidation in an incorrect user storage? Or I do not know what else could explain why I have to call \Drupal::service('entity_type.manager')->getStorage('user')->resetCache(); manually.
Fun fact, the test that required this fix runs the user synchronization in the UI. There is an another test which runs the synchronization with Drush and that test does not require this fix.
Closed: duplicate
10.0 ✨
Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This is the same issue as
#2066993: Use \Drupal consistently in tests →
. $this->container can be state after a request against the tested site, but \Drupal gets refreshed. We haven't been able to figure out a way to keep $this->container fully in sync, so the recommendation is to use \Drupal everywhere, except that issue isn't finished yet.