Skip to content
Benchmarking

feat(launch profiling): use dedicated traces instead of auto perf traces #4854

Sign in to view logs

feat(launch profiling): use dedicated traces instead of auto perf traces

feat(launch profiling): use dedicated traces instead of auto perf traces #4854

Triggered via pull request February 15, 2024 08:44
@armcknightarmcknight
synchronize #3621
armcknight/feat/launch-profiling3-create-dedicated-launch-traces
Status Failure
Total duration 25m 13s
Artifacts 2

benchmarking.yml

on: pull_request
Build app and test runner
1m 45s
Build app and test runner
Collect app metrics
7m 47s
Collect app metrics
Matrix: Run benchmarks on Sauce Labs
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
Run benchmarks on Sauce Labs (High-end device)
Process completed with exit code 1.
Run benchmarks on Sauce Labs (Low-end device)
Process completed with exit code 1.
Collect app metrics
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-java@v3, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Artifacts

Produced during runtime
Name Size
DerivedData-Xcode Expired
18.8 MB
app-sdk-metrics-results Expired
711 Bytes