Repository navigation
Stabilize integration tests - #898
Conversation
SummaryThe following content is AI-generated and provides a summary of the pull request: Improve Integration Test Resilience for Malware ScansBug Fixes🐛 Stabilized integration tests affected by intermittent malware scan service timeouts. Generic integration tests now retry failed tests up to two times, while malware scan polling uses a configurable timeout that defaults to one minute. Changes
PR Bot InformationVersion:
|
![hyperspace-pr-bot[bot]](https://avatars.githubusercontent.com/u/2531208?s=60&v=4){kind=small}
There was a problem hiding this comment.
The configurable timeout is integrated consistently, but the action should safely pass the input and scope retries to malware-dependent tests so unrelated failures remain visible.
PR Bot Information
Version: 1.32.6
- LLM:
gpt-5.6-sol - File Content Strategy: Full file content
- Correlation ID:
22609f80-c3c4-11f1-88a1-0175817f3aed - Agent Instructions:
- Event Trigger:
pull_request.opened
0602bfe to
79a64b4
Compare
tomk8r
left a comment
tomk8r
left a comment
There was a problem hiding this comment.
Regarding the PT60S suggestion: It might be slightly cleaner to use consistent units, but it's not critical.
The Hyperspace security suggestion should be committed.
79a64b4 to
a4535e3
Compare
3 participants
Currently, for each CI run on a PR, we get failing integration tests.
The root cause is that the malware service does not answer to the scan request.
As a mitigation, I configured the test runner to retry failed tests. With the retry, we have a good chance to get a green job.
I also made the timeout configurable, but in the end decided to stay with the one minute timeout, because successful scans finish within seconds.