mocobeta opened a new pull request #755:
URL: https://github.com/apache/lucene/pull/755


   I encountered several times a "disk full" error when running the smoke 
tester.
   From my observation, there is a test that (intentionally) creates very large 
index files. It might be helpful to have a notice about that in the rc 
announcing mails and encourage to explicitly use `--tmp-dir` option to avoid 
unnecessary retries.
   
   Here is a snapshot of the disk usage in a smoke tester run.
   ```
   $ dust -b ~/tmp/smoketester/
     47M   ┌── lucene-9.1.0-src.tgz
     64M   ├── lucene-9.1.0.tgz
     37M   │     ┌── test-framework
     59M   │     │     ┌── lucene-9.1.0-SNAPSHOT-itests
     59M   │     │   ┌─┴ packages
     59M   │     │ ┌─┴ build
     59M   │     ├─┴ distribution
     51M   │     │ ┌── build
     63M   │     ├─┴ backward-codecs
    125M   │     │   ┌── site
    125M   │     │ ┌─┴ build
    125M   │     ├─┴ documentation
     55M   │     │ ┌── nori
    133M   │     ├─┴ analysis
    3.0G   │     │           ┌── _0.cfs
    4.0G   │     │           ├── _0.fdt
    7.1G   │     │         ┌─┴ 4GBStoredFields-001
    7.1G   │     │       ┌─┴ 
lucene.index.Test4GBStoredFields_1FCE4B52E7A84AF3-001
    7.1G   │     │     ┌─┴ tests-tmp
    7.1G   │     │   ┌─┴ tmp
    7.1G   │     │ ┌─┴ build
    7.1G   │     ├─┴ core
    7.6G   │   ┌─┴ lucene
    7.6G   │ ┌─┴ lucene-9.1.0
    7.6G   ├─┴ unpack
    7.7G ┌─┴ smoketester
   ```
   
   I didn't (couldn't) test this but just grepped the scripts to find where to 
change; would you tell me the correct file if I'm modifying the wrong file.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to