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-78292 Always fetch head revision during publishing the layout, regardless of user's recent objects #58441
Conversation
…gardless of user's recent objects
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 1 minute 21 seconds 810 msClick here for more details.Base Branch:Branch Name: master Sender Branch:Branch Name: pr-2039 1 Successful Jobs:For more details click here. |
❌ ci:test:relevant - 4 out of 7 jobs passed in 59 minutes 39 seconds 861 msClick here for more details.Base Branch:Branch Name: master Copied in Private Modules Branch:Branch Name: master-private 3 Failed Jobs:4 Successful Jobs:For more details click here.Failures unique to this pull:
Failures in common with acceptance upstream results at 42a9ddf:
|
ci:test:relevant |
@matethurzo sorry for the noise in CI, see loop post for details |
❌ ci:test:relevant - 5 out of 7 jobs passed in 53 minutes 16 seconds 41 msClick here for more details.Base Branch:Branch Name: master Copied in Private Modules Branch:Branch Name: master-private 2 Failed Jobs:5 Successful Jobs:
For more details click here.Failures unique to this pull:
For upstream results, click here. |
Merged. Thx. |
@Ithildir do you know why CI is asking for this? |
Gradle is complaining because a module contains an integration test which depends from |
No description provided.