-
Notifications
You must be signed in to change notification settings - Fork 13.6k
[clang] pch-related test failures: fatal error: file './module.modulemap' has been modified since the module file '...' w as built: content changed
#96379
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
clang:modules
C++20 modules and Clang Header Modules
Comments
fatal error: file './module.modulemap' has been modified since the module file '/var/tmp/portage/sys-devel/clang-19.0.0_pre20240622/work/x/y/clang-abi_x86_32.x86/test/Modules/Output/implicit-module-no-timestamp.cpp.tmp/3RPMK39W91IAT/a-2ZILJK6X9KN22.pcm' w as built: content changed
fatal error: file './module.modulemap' has been modified since the module file '...' w as built: content changed
@llvm/issue-subscribers-clang-modules Author: Michał Górny (mgorny)
I'm guessing multiple tests are using the same output file and therefore there's some race condition there:
|
Full log: llvm.txt.gz |
I was able to reproduce it multiple times in a row, so this doesn't seem like a random fluke. I'm going to try bisecting it. |
fatal error: file './module.modulemap' has been modified since the module file '...' w as built: content changed
fatal error: file './module.modulemap' has been modified since the module file '...' w as built: content changed
Bisect points to:
CC @MaskRay This might actually be a bug on 32-bit arches, I'm trying pure 64-bit now. |
AlexisPerry
pushed a commit
to llvm-project-tlp/llvm-project
that referenced
this issue
Jul 9, 2024
https://reviews.llvm.org/D67249 added content hash (see -fvalidate-ast-input-files-content) using llvm::hash_code (size_t). The hash value is 32-bit on 32-bit systems, which was unintentional. Fix llvm#96379: llvm#96136 switched the hash function to xxh3_64bit but did not update the ContentHash type, leading to mismatch between ASTReader and ASTWriter.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm guessing multiple tests are using the same output file and therefore there's some race condition there:
The text was updated successfully, but these errors were encountered: