-
Notifications
You must be signed in to change notification settings - Fork 461
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
Refresh Running Experiment Cache after abort one Experiment #28507
Labels
LTS : Next
Ticket that will be added to LTS
Merged
NW Removed
QA : Approved
QA : Passed Internal
Release : 24.05.20
Bug- Fixing
Team : Falcon
Type : Defect
Comments
freddyDOTCMS
added a commit
that referenced
this issue
May 13, 2024
github-merge-queue bot
pushed a commit
that referenced
this issue
May 15, 2024
#28541) ### Proposed Changes * Clean the Running Experiment List cache after cancel one Experiment https://github.com/dotCMS/core/pull/28541/files#diff-5aa71567ff53ee229d25c2386cce3169c657f37a3e04cf27b75b3fd029537a7cR1469 * Refactor assertCachedRunningExperiments test util method We need compare the size of the list and check if the Cache list is null https://github.com/dotCMS/core/pull/28541/files#diff-fad94d09d18233a324e27a58867ff9f9967a3106d0cff91d359fb2327967fbecR481-R485 * Update the cancel Experiment test to check that the Running Experiment List cache is empty after cancel an Experiment https://github.com/dotCMS/core/pull/28541/files#diff-fad94d09d18233a324e27a58867ff9f9967a3106d0cff91d359fb2327967fbecR4014-R4027 ### Checklist - [x] Tests
PR: #28541 |
Passed Internal QA: Running experiments cache properly invalidated upon aborting a running experiment. |
Approved: Tested on trunk_aaa6d05, Docker, macOS 13.0, FF v124.0.2 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
LTS : Next
Ticket that will be added to LTS
Merged
NW Removed
QA : Approved
QA : Passed Internal
Release : 24.05.20
Bug- Fixing
Team : Falcon
Type : Defect
Parent Issue
No response
Problem Statement
After abort an Experiment it is keep on the Running Experiment Cache so it means that a User can be still assigned to the Experiment even after it was aborted
Steps to Reproduce
Acceptance Criteria
dotCMS Version
latest in master
Proposed Objective
Core Features
Proposed Priority
Priority 2 - Important
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
The text was updated successfully, but these errors were encountered: