Closed guyarb closed 3 days ago
[Fast Unit Tests Report]
On pipeline 38095466 (CI Visibility). The following jobs did not run any unit tests:
If you modified Go files and expected unit tests to run in these jobs, please double check the job logs. If you think tests should have been executed reach out to #agent-devx-help
Use this command from test-infra-definitions to manually test this PR changes on a VM:
inv create-vm --pipeline-id=38095466 --os-family=ubuntu
Note: This applies to commit f6002246
Setup event stream monitoring (if needed) and process monitor only once per a suite run. In the leaf tests we register and de-register dedicated callbacks to verify the tests are working. Thus, we don't have to create over and over again the event monitoring for every leaf test.
Can you share in the PR description the impact of this change? (before and after)
/merge
:steam_locomotive: MergeQueue: pull request added to the queue
The median merge time in main
is 25m.
Use /merge -c
to cancel this operation!
Setup event stream monitoring (if needed) and process monitor only once per a suite run. In the leaf tests we register and de-register dedicated callbacks to verify the tests are working. Thus, we don't have to create over and over again the event monitoring for every leaf test.
Can you share in the PR description the impact of this change? (before and after)
overall no impact the first commit reduced about 1m from the total time of the tests, but the second commit consumed most of it
What does this PR do?
Motivation
The setup/teardown time for the event monitoring, which takes 10s. Thus, running event monitoring tests are very expensive
Additional Notes
Possible Drawbacks / Trade-offs
Describe how to test/QA your changes