Updated Azure Pipelines pool #150
Conversation
There was a problem hiding this comment.
Should we now remove the GitHub action to run virtual tests, that we recently added? The full build should now cover everything and it seems repetitive to keep both just for reducing dependency on Azure.
Those are msft internal instructions while Azure Pipelines is an App already installed at Organization level (https://github.com/apps/azure-pipelines) |
Makes sense to me. Thoughts @ivarprudnikov ? |
|
I would not remove Github action just yet as it is quite fast and acts as a
fallback in a case azure pipeline gets removed or similar.
…On Tue 5 Sep 2023 at 12:51, Vincenzo Mauro ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In test/test_load.py
<#150 (comment)>
:
> @@ -11,7 +11,7 @@
from pyscitt.client import Client
NUM_CLAIMS = 100
-LOCUST_PEAK_USERS = 500
+LOCUST_PEAK_USERS = 100
LOCUST_USERS_SPAWN_RATE = 10
Thanks, decreased to 5
—
Reply to this email directly, view it on GitHub
<#150 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIA7YTG6XSUMZFUWQI7RJ3XY4G23ANCNFSM6AAAAAA4LT3QBA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
vimauro
dismissed
ivarprudnikov’s stale review
Those are msft internal instructions while Azure Pipelines is an App already installed at Organization level (https://github.com/apps/azure-pipelines)
I have set up a new agent pool to be used by Azure Pipelines since the old one was removed.
This PR makes use of the new pool and restores the LOCUST_PEAK_USERS to 100 which is the original value while we investigate why 500 fails in SGX with no prefix tree.