[all-commits] [llvm/llvm-project] 7d1cc5: [LLDB] Fix race/collision in TestGlobalModuleCache...

[cmtice via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 7d1cc51305618bfe2d63603d9cec3a4a4c147a10
      https://github.com/llvm/llvm-project/commit/7d1cc51305618bfe2d63603d9cec3a4a4c147a10
  Author: cmtice <cmtice at google.com>
  Date:   2026-06-09 (Tue, 09 Jun 2026)

  Changed paths:
    M lldb/test/API/python_api/global_module_cache/TestGlobalModuleCache.py

  Log Message:
  -----------
  [LLDB] Fix race/collision in TestGlobalModuleCache.py (#202731)

https://github.com/llvm/llvm-project/pull/201561 sped up the test so
much that, on very fast machines, there is now a collision. The two
different a.out files get created with the exact same timestmp, which
confuses the module caching and can result in odd test failures:

make: Leaving directory
'/build/work/8a9b9199309f6c504f12c8bdaef77b319248/google3/tmp/lldb-test-build.noindex/python_api/global_module_cache/TestGlobalModuleCache.test_TwoTargetsOneDebugger_dwarf'

Unable to load lldb extension module. Possible reasons for this include:
  1) LLDB was built with LLDB_ENABLE_PYTHON=0
2) PYTHONPATH and PYTHONHOME are not set correctly. PYTHONHOME should
refer to
the version of Python that LLDB built and linked against, and PYTHONPATH
should contain the Lib directory for the same python distro, as well as
the
     location of LLDB's site-packages folder.
3) A different version of Python than that which was built against is
exported in
     the system's PATH environment variable, causing conflicts.
4) The executable
'/build/work/8a9b9199309f6c504f12c8bdaef77b319248/google3/runfiles/google3/third_party/llvm/llvm-project/lldb/lldb'
could not be found. Please check
     that it exists and is executable.

This PR fixes that by future-dating the second a.out file.

AI-assisted by Gemini.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications