potiuk commented on pull request #20087:
URL: https://github.com/apache/airflow/pull/20087#issuecomment-1002543301


   Try with those args (and use ./breeze as it contains .coveragerc for example:
   
   ```
   if [[ ${ENABLE_TEST_COVERAGE:="false"} == "true" ]]; then
       EXTRA_PYTEST_ARGS+=(
           "--cov=airflow/"
           "--cov-config=.coveragerc"
           "--cov-report=xml:/files/coverage-${TEST_TYPE}-${BACKEND}.xml"
       )
   fi
   ```
   
   I just repeated that, and results are the same. Steps to reproduce:
   
   Setup:
   
   1) `./breeze stop` (stop all containers)
   2) `./breeze --db-reset --backend sqlite` (starts breeze in basic sqlite 
configuration with reseting the db)
   3)  Run `docker stats` in separate terminal
   4) Run `pytest ./tests/providers/cncf/kubernetes/hooks/test_kubernetes.py 
./tests/jobs/test_backfill_job.py` to "warm the caches" 
   
   Once you do it, it very reproducible:
   
   Test a) - without coverage:
   
   `pytest ./tests/providers/cncf/kubernetes/hooks/test_kubernetes.py 
./tests/jobs/test_backfill_job.py`
   
   
https://user-images.githubusercontent.com/595491/147656637-6ad880e1-9f2b-4364-915a-cd5c92aa58c0.mp4
   
   Memory tops ~ 156 MB and drops right after the tests fiinish.
   
   Test b) - with coverage:
   
   `pytest ./tests/providers/cncf/kubernetes/hooks/test_kubernetes.py 
./tests/jobs/test_backfill_job.py --cov=airflow/ --cov-config=.coveragerc 
--cov-report=xml:/files/coverage-test.xml`
   
   
https://user-images.githubusercontent.com/595491/147656618-c550ae90-521c-40cd-b842-32172a2ab94a.mp4
   
   Durint the test memory usage is very similar - but when the tests are 
finishing (I guess output report is prepared) the memory used goes quickly up 
to more than 230 MB  just before dropping (about 0:19 of the video). This 
effect is non-existing in case coverate is disabled.
   
   This is fully reproducible.
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   


-- 
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]


Reply via email to