-
Notifications
You must be signed in to change notification settings - Fork 14
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
Incorporated old dev-branch changes #27
Conversation
Can we test if the branch is working before merging to make sure we haven't omitted anything in this whole process? Also, the CI fails because |
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.
The main readme contains a lot of useful information, thanks a lot!
I suggest shortening the main readme, moving the auxiliary script description to a separate doc in the docs/
folder (e.g., moving the health checking scripts there) but leaving a reference to that doc in the main readme.
More feedback will follow today.
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 haven't finished my pass but I am going to continue working on it in next few days (probably Sunday). Please go ahead and apply comments from me and Lazar.
@@ -59,5 +59,6 @@ server_exec() { | |||
echo 'Done setting up monitoring components' | |||
|
|||
server_exec 'cd loader; bash scripts/setup/patch_init_scale.sh' | |||
server_exec 'cd loader/data; wget -q -O traces.zip "https://www.dropbox.com/scl/fo/x4ct0kzzjnn6we7h31md4/h?dl=1&rlkey=llxj5f5i3uz9rvd9h3m573ueg" && unzip traces.zip -d traces' |
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 may want to have a tiny trace for running tests in CI. it should also be in Git LFS but separately from the main archive.
Thank you all! |
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.
When addressing comments for a PR with so many changes, please follow the following protocol, which would allow us to inspect every change carefully. For each comment each reviewer makes, (1) push the changes if needed, (2) respond to the comment so the reviewer can take a look and see if the reviewer agrees with the change, indicating that by resolving the comment. Since we are doing that with many comments in batches, this protocol should not cause much delay in finalizing the code.
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.
ok, I finished my pass. Please address all the comments now, starting with the parser, then load generator, results parser, etc. Please stage it (i.e., one-two logical components at a time) so that we can parallelize implementation and code review efforts effectively.
I don't think I was able to scrutinize everything so we'll need to iterate after this PR is merged.
@@ -0,0 +1,13 @@ | |||
#!/usr/bin/env bash | |||
CONFIG_FILE=$1 |
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.
as mentioned in deploy.go. this functionality should be written in Golang.
Thank you all. All suggestions applied, except for those I don't know how to. |
Signed-off-by: Lazar Cvetković <[email protected]>
Signed-off-by: Hongyu <[email protected]>
Signed-off-by: Hongyu <[email protected]>
Signed-off-by: Lazar Cvetković <[email protected]>
Signed-off-by: Lazar Cvetković <[email protected]>
Signed-off-by: Lazar Cvetković <[email protected]>
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.
the commit LGTM
Signed-off-by: Lazar Cvetković <[email protected]>
Signed-off-by: Lazar Cvetković <[email protected]>
Signed-off-by: Lazar Cvetković <[email protected]>
Signed-off-by: Lazar Cvetković <[email protected]>
Signed-off-by: Lazar Cvetković <[email protected]>
Signed-off-by: Lazar Cvetković <[email protected]>
Signed-off-by: Lazar Cvetković <[email protected]>
Signed-off-by: Lazar Cvetković <[email protected]>
Signed-off-by: Lazar Cvetković <[email protected]>
Signed-off-by: Lazar Cvetković <[email protected]>
Signed-off-by: Lazar Cvetković <[email protected]>
Signed-off-by: Lazar Cvetković <[email protected]>
Signed-off-by: Lazar Cvetković <[email protected]>
Signed-off-by: Hongyu <[email protected]>
Thanks everyone! I've applied the suggestions except for those asking for more detailed documentation. I will add them gradually. The PR is good to me as well! |
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.
This PR cannot be merged before the remaining comments are addressed. Most of them are really easy to address (just add appropriate comments).
Duration and memory characteristics choice logic has a bug. These issues have the highest priority to fix.
Also, if you need to argue with the review, please discuss potential concerns constructively.
as far as I understand, this PR does not change the integration tests you wrote, it just runs them in the CI as opposed to locally. Please investigate why the tests break and fix them. If you have any questions on the github actions side, please let me know and I'd try to explain. |
Signed-off-by: Hongyu <[email protected]>
Signed-off-by: Dohyun Park <[email protected]>
Signed-off-by: Dohyun Park <[email protected]>
Signed-off-by: Hongyu <[email protected]>
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.
Excellent job! Thank you for improving the comments and readability and for adding a test for the parser.
I left quite minor comments but they should not take more than 30min to fix altogether.
d065c94
to
6ce03a7
Compare
Signed-off-by: Hongyu <[email protected]>
The warm-up process has changed and been improved according to our discussions, as well as the trace mode.
Implementation Notes ⚒️
MaxMaxAlloc()
that's the opposite of max-min fairness.10.X.Y.Z
so that no one needs to go to the cloudlab jail.External Dependencies 🍀
Breaking API Changes⚠️
pkg\atom.go
Resolves #20, #21