-
Notifications
You must be signed in to change notification settings - Fork 99
Conversation
@javiertoledo
javiertoledo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, very useful!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So bad we're still relying on this, as this package has been abandoned. Just as a reminder for ourselves, there's a pending issue related to finding an alternative or building this capability within Booster #934
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we add this call on the "integration/azure" script (line 85)?
bcad4f1 to
672334e
Compare
..._test_azure # Conflicts: # package-lock.json # packages/framework-integration-tests/package.json
👇 Click on the image for a new way to code review
Review these changes using an interactive CodeSee Map
Legend
CodeSee Map legend
javiertoledo
commented
Mar 2, 2023
/integration sha=792b5d6bf320704a207d5acc1ef92b1cf2284cac
⌛ Integration tests are running...
Check their status here 👈
❌ Oh no! Integration tests have failed
javiertoledo
commented
Mar 2, 2023
/integration sha=f7a32b7d18aaa1b7d0c961433089a3edcd42fb26
⌛ Integration tests are running...
Check their status here 👈
❌ Oh no! Integration tests have failed
..._test_azure # Conflicts: # common/config/rush/pnpm-lock.yaml
javiertoledo
commented
Oct 2, 2023
/integration sha=3e61b829586e58a7c565b7c83ed144ee0d7fdd6a
⌛ Integration tests are running...
Check their status here 👈
❌ Oh no! Integration tests have failed
2 similar comments
❌ Oh no! Integration tests have failed
❌ Oh no! Integration tests have failed
Uh oh!
There was an error while loading. Please reload this page.
Description
In this PR we are configuring the load tests for the Azure provider. Basically we have reverted serverless framework to the old version because it is not compatible with Serverless Artillery and then we have had to increase the timeout in the tests and adapted the load to be manageable by Azure. We achieve 200 requests/sec during 10 sec followed by 400 req/sec for 10sec.
Changes
Checks