We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
Running the indexer from scratch I noticed repeated messages within single indexer run:
# grep linux-uek /opengrok-upgrade/log/reindex.log | grep history 15:22:00 INFO: Creating historycache for /ws-local-upgrade/linux-uek-4.1 (GitRepository) without renamed file handling 16:23:06 INFO: Done historycache for /ws-local-upgrade/linux-uek-4.1 (took 1:01:06) 04:53:51 INFO: Creating historycache for /ws-local-upgrade/linux-uek-SPARC (GitRepository) without renamed file handling 06:29:42 INFO: Done historycache for /ws-local-upgrade/linux-uek-SPARC (took 1:35:51) 11:55:42 INFO: Creating historycache for /ws-local-upgrade/linux-uek-4.1 (GitRepository) without renamed file handling 11:56:06 INFO: Done historycache for /ws-local-upgrade/linux-uek-4.1 (took 23.331 seconds) 14:06:29 INFO: Creating historycache for /ws-local-upgrade/linux-uek-SPARC (GitRepository) without renamed file handling 14:07:00 INFO: Done historycache for /ws-local-upgrade/linux-uek-SPARC (took 31.150 seconds)
This is going to skew the indexer statistics for #3245.
Possibly this is related to ensureHistoryCacheExists() called in the 2nd phase of indexing.
ensureHistoryCacheExists()
The text was updated successfully, but these errors were encountered:
be content with just history cache directory in ensureHistoryCacheExi…
6b3c252
…sts() fixes oracle#3260
701fae2
7f6c5bb
…sts() fixes #3260
vladak
No branches or pull requests
Uh oh!
There was an error while loading. Please reload this page.
Running the indexer from scratch I noticed repeated messages within single indexer run:
This is going to skew the indexer statistics for #3245.
Possibly this is related to
ensureHistoryCacheExists()
called in the 2nd phase of indexing.The text was updated successfully, but these errors were encountered: