-
-
Notifications
You must be signed in to change notification settings - Fork 520
Description
After the new unit-tests for analyzers (https://github.com/intelowlproject/IntelOwl/actions/runs/16919533634/job/47941937348?pr=2886), we can see that the full pipeline is quite slow but that's not caused by the added tests. There are some tests that take a lot of seconds while they shouldn't. We should list and review them one by one to reduce the amount of time required to run the full pipeline.
Examples:
test_subclasses (tests.api_app.ingestors_manager.test_classes.IngestorTestCase.test_subclasses) ... ok-dokey (18.214010s)
test_pull (tests.api_app.analyzers_manager.test_views.AnalyzerConfigViewSetTestCase.test_pull) ... ok-dokey (15.476543s)
test_urls (tests.api_app.analyzers_manager.file_analyzers.test_doc_info.DocInfoTestCase.test_urls) ... ok-dokey (36.010417s)
test_analyze_file__pcap (tests.api_app.test_api.ApiViewTests.test_analyze_file__pcap)....ok-dokey (7.632454s) -> this one fails too
test_job_rescan__observable_playbook (tests.api_app.test_api.ApiViewTests.test_job_rescan__observable_playbook) ... ok-dokey (13.045382s)