Skip to content
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

[SR-11729] [llbuild] Add Chromium Tracing as export format option to llbuild-analyze #781

BenchR267 opened this issue Nov 7, 2019 · 0 comments


Copy link

@BenchR267 BenchR267 commented Nov 7, 2019

Previous ID SR-11729
Radar rdar://problem/56980059
Original Reporter @BenchR267
Type New Feature
Additional Detail from JIRA
Votes 0
Component/s llbuild
Labels New Feature, StarterBug
Assignee None
Priority Medium

md5: e95651ecd257351f56e234e25e728425

Issue Description:

llbuild-analyze is a local package in llbuild which offers a command line interface for calculating the critical path given a build database. The critical path of a build defines the chain of dependent tasks that has the longest duration when adding up the individual durations of those tasks. The tool offers to export the critical path as a JSON file which can then be used for further investigation.
Adding more serialization options would result in more actionable workflows. This issue tracks adding Chromium Tracing as an export schema option which would allow users to open the created critical path file and view it in their Chrome browser or other tool which is able to read and visualize the format.
The format is well defined and all the necessary information should be available in the CriticalBuildPath object that gets returned by the algorithm - it contains all tasks that were part of the build (including their timing information) and the dependency chain that forms the critical path.
The tool lives in products/llbuild-analyze/Sources/CriticalPathTool.swift and offers the basic infrastructure of supporting multiple export formats. Those consist of json and GraphViz at the moment.

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
@shahmishal shahmishal transferred this issue from apple/swift May 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

1 participant