-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Load test proc mount in a workspace #8234
Conversation
@@ -19,4 +19,5 @@ for COMPONENT in tests/components/*; do | |||
go test -trimpath -ldflags="-buildid= -w -s" -c -o bin/"$OUTPUT".test ./"$COMPONENT" | |||
done | |||
|
|||
go test -trimpath -ldflags="-buildid= -w -s" -o bin/workspace -c ./tests/workspace | |||
echo building test tests/workspace | |||
go test -trimpath -ldflags="-buildid= -w -s" -o bin/workspace.test -c ./tests/workspace |
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.
It seems that the workspace test had not been run before, but I didn't know why.
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.
ref:
Line 14 in 30da763
for i in $(find /tests/ -name "*.test" | sort); do |
numberOfMount = 500 | ||
parallel = 5 |
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.
There was no material to determine if it was a reasonable number. Do you have a good idea?
If it takes too long and becomes a problem, I'd consider adding an annotation for stress testing.
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.
We have used 1000 mounts before.
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.
I was going to go with 1000 at first, but I'm having trouble finding any evidence that 1000 and 500 are different. The larger the number, the longer it takes to test.
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.
Then lets go with 500 for now. If we see this problem again and the test does not show it, we can increase the number of iterations.
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.
👍
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.
@Furisto Thanks for your review!
wertf passed this integration test. |
Codecov Report
@@ Coverage Diff @@
## main #8234 +/- ##
==========================================
- Coverage 12.31% 11.17% -1.14%
==========================================
Files 20 18 -2
Lines 1161 993 -168
==========================================
- Hits 143 111 -32
+ Misses 1014 880 -134
+ Partials 4 2 -2
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Description
Related Issue(s)
Fixes #8098
How to test
Release Notes
Documentation
No