Skip to content
Pull Request

fix: correct rendering issue with Rokt placement holder #45

Sign in to view logs

fix: correct rendering issue with Rokt placement holder

fix: correct rendering issue with Rokt placement holder #45

Re-run triggered June 9, 2025 20:13
@Mansi-mParticleMansi-mParticle
#30
fix/rokt-placement-holder-issue
Status Success
Total duration 4m 44s
Artifacts 4
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

pull-request.yml

on: pull_request
Pull Request Check  /  ...  /  Unit Tests Maven
2m 36s
Pull Request Check / Run regression / Unit Tests Maven
Pull Request Check  /  ...  /  Unit Tests Development
3m 44s
Pull Request Check / Run regression / Unit Tests Development
Pull Request Check  /  ...  /  Lint Checks Maven
2m 30s
Pull Request Check / Run regression / Lint Checks Maven
Pull Request Check  /  ...  /  Lint Checks Development
4m 32s
Pull Request Check / Run regression / Lint Checks Development
Pull Request Check  /  ...  /  Kotlin Lint Checks Maven
53s
Pull Request Check / Run regression / Kotlin Lint Checks Maven
Pull Request Check  /  ...  /  Kotlin Lint Checks Development
3m 37s
Pull Request Check / Run regression / Kotlin Lint Checks Development
Pull Request Check  /  ...  /  Confirm that target branch for PR is development or build/
0s
Pull Request Check / Check PR for correct target branch / Confirm that target branch for PR is development or build/
Pull Request Check  /  ...  /  Check PR for semantic branch name
0s
Pull Request Check / Check PR for semantic branch name / Check PR for semantic branch name
Pull Request Check  /  ...  /  Check PR for semantic title
0s
Pull Request Check / Check PR for semantic title / Check PR for semantic title
Pull Request Check  /  ...  /  Save PR Number for Dependabot Automerge
0s
Pull Request Check / Save PR Number for Dependabot Automerge / Save PR Number for Dependabot Automerge
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 8 warnings
Pull Request Check / Run regression / Lint Checks Maven
Gradle build failed: see console output for details
Pull Request Check / Run regression / Unit Tests Maven
Gradle build failed: see console output for details
Pull Request Check / Run regression / Kotlin Lint Checks Maven
Restore Gradle distribution 7.5.1 failed: Error: getCacheEntry failed: Cache service responded with 503
Pull Request Check / Run regression / Lint Checks Maven
No files were found with the provided path: ./**/build/reports/**. No artifacts will be uploaded.
Pull Request Check / Run regression / Lint Checks Maven
Restore Gradle distribution 7.5.1 failed: Error: getCacheEntry failed: Cache service responded with 503
Pull Request Check / Run regression / Kotlin Lint Checks Development
Restore Gradle distribution 7.5.1 failed: Error: getCacheEntry failed: Cache service responded with 503
Pull Request Check / Run regression / Unit Tests Maven
Restore Gradle distribution 7.5.1 failed: Error: getCacheEntry failed: Cache service responded with 503
Pull Request Check / Run regression / Unit Tests Maven
No files were found with the provided path: ./**/build/reports/**. No artifacts will be uploaded.
Pull Request Check / Run regression / Unit Tests Development
Restore Gradle distribution 7.5.1 failed: Error: getCacheEntry failed: Cache service responded with 503
Pull Request Check / Run regression / Lint Checks Development
Restore Gradle distribution 7.5.1 failed: Error: getCacheEntry failed: Cache service responded with 503

Artifacts

Produced during runtime
Name Size Digest
lint-results-development Expired
23.1 KB
sha256:5241c36f6039f725134c6fd64bc0fb8d147b1877a4dc8d5e2795c4d4f9dcd591