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
LPS-96762 Add MVCCVersion to DL Objects #75564
Conversation
CI is automatically triggering "ci:test:sf" and "ci:test:relevant" for this pull to run Source Formatter and relevant tests. Comment "ci:test" to run the full PR Tester for this pull. |
✔️ ci:test:sf - 1 out of 1 jobs passed in 3 minutes 55 seconds 219 msClick here for more details.Base Branch:Branch Name: master Sender Branch:Branch Name: pr-333 1 Successful Jobs:For more details click here. |
❌ ci:test:relevant - 0 out of 1 jobs passed in 2 hours 13 minutes 29 seconds 741 msClick here for more details.Base Branch:Branch Name: master Copied in Private Modules Branch:Branch Name: master-private 1 Failed Jobs:For more details click here.Failures unique to this pull:
For upstream results, click here. |
ci:test:relevant |
@achaparro Can you resend on top of achaparro#335 I made some changes, but I found UpgradeMVCCVersionTest very weird.
vs.
Is the difference in case on purpose? I also re-read the test over and over again but could not figure out what it was doing? I mean, how is it testing module vs. portal upgrades? Please resend. Thx |
cc/ @AliciaGarciaGarcia