-
-
Notifications
You must be signed in to change notification settings - Fork 38
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
Manage workload caches #79
Conversation
a51dc1a
to
50449ee
Compare
Reviewer: @hangshao0 |
Please add more details in your commit message. |
The test passes 5x Grinder on Internal Jenkins (Link shared with Hang on Slack). |
There is a failure in the Grinder run at Adopt: https://ci.adoptopenjdk.net/view/Test_grinder/job/Grinder/906/tapResults/ From 62.WL3.stderr log file:
|
5x Grinder at openj9 passes : https://ci.eclipse.org/openj9/view/Test/job/Test-Grinder/245/console |
Since the PR passes in internal Jenkins 5x Grinder and also OpenJ9 5x Grinder, it should be ready to merge. @smlambert - Once you have a minute, please merge this PR. |
No. I don't think it is related to this change. |
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, noted some spelling / minor stuff
// caches that might exist on the machine where the test is running). So, we should attempt | ||
// to destroy only the test-related cache we are given. | ||
if (info.getCacheName() == null) { | ||
// We want to only delete the worklaod caches here. |
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.
workload vs worklaod
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.
Corrected.
// We want to only delete the worklaod caches here. | ||
// Any cache that might be listed in the default location - created | ||
// or owned by other processes should be ignored. | ||
// Cache created and used by the SharedClassesCacheCheceker process |
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.
SharedClassesCacheChecker vs SharedClassesCacheCheceker
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.
Thanks. Fixed.
@@ -195,7 +198,7 @@ boolean delete() { | |||
rv = false; | |||
break; | |||
} | |||
this.alreadySuccesfullyDeletedCaches.add(cacheName); | |||
this.alreadySuccesfullyDeletedCaches.add(info.getCacheName()); |
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.
Is there a reason to switch to use info.getCacheName() on line 201, instead of cacheName defined up on line 163?
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.
Ah.. Missed that. Updated!
Signed-off-by: Mesbah_Alam@ca.ibm.com <Mesbah_Alam@ca.ibm.com>
50449ee
to
57aca5f
Compare
Run SharedClassesCacheChecker with only workload caches
Fixes: #78
Signed-off-by: Mesbah_Alam@ca.ibm.com Mesbah_Alam@ca.ibm.com