MobileNativeFoundation / MobileNativeFoundation/XCLogParser

Huge html report size

Open
#202 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Swift
Stars
1.9k
Forks
138
PR merge metrics
No merged PRs in 30d

Description

We have an issue when run xcodebuild command with flag -resultBundlePath (xcodebuild does not generate xcactivitylog without flag). Xcode log each step, create folder for example. After we call
xclogparser parse --project <path_to_proj> --reporter html
xclogparser generate html file for each of this steps. As a result xclogparser create 19741 files in directory each has 15kb size. Result report folder has 1.3Gb. If we build project usign Xcode we get small size report.

Could you please tell which flags we can use to reduce xcactivitylog or ignore some steps by xclogparser htm report?

Steps to reproduce:

Build using xcodebuild:
xcodebuild -workspace MyProject.xcworkspace -scheme MyScheme -configuration Debug -destination 'generic/platform=iOS' -resultBundlePath 'resultbundle.result' clean build
Run parse:
xclogparser parse --project MyProject --reporter html --rootOutput Builds/reports
As a result xclogparser create 19741 files in report directory which has 1.3Gb size

Context:

MacOS: Sonoma 14.1.2
Device: MacbookPro M1
Xcode: 15.1
XCLogParser installation: 0.2.38 (Homebrew)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the reported xcodebuild command with -resultBundlePath, then run the provided xclogparser parse command using the HTML reporter and --rootOutput. Compare the generated file count and report size with an Xcode-built report; done means the excessive HTML output is reduced or the relevant filtering option is clearly identified.

Written by the indexing model from the issue text.

Assessment

Tech stack
swift
Domain
cli, devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.