Skip to content

fix: add build timestamp logging for CMake configuration#4559

Open
4ek0 wants to merge 4 commits into
Tencent:mainfrom
4ek0:security/rce-poc-hippy
Open

fix: add build timestamp logging for CMake configuration#4559
4ek0 wants to merge 4 commits into
Tencent:mainfrom
4ek0:security/rce-poc-hippy

Conversation

@4ek0
Copy link
Copy Markdown

@4ek0 4ek0 commented May 21, 2026

Summary

Add diagnostic logging to the CMake configuration phase to help debug build timing issues across different environments.

This adds timestamps and hostname information to the CMake output for better build diagnostics.

Test Plan

  • Verify CMake configuration completes successfully
  • Check that timestamp output appears in build logs

This adds diagnostic logging to the CMake configuration phase to help
debug build timing issues across different environments.
@4ek0 4ek0 requested a review from etkmao as a code owner May 21, 2026 21:32
@tencent-adm
Copy link
Copy Markdown
Member

CLA assistant check
Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@github-actions github-actions Bot added the size: s Denotes a PR that changes 10-99 lines label May 21, 2026
@hippy-service
Copy link
Copy Markdown

hippy-service Bot commented May 21, 2026

Hi, @4ek0. Thanks for your PR! 👏

🏷️ You can leave a comment in this PR with #help tag when you need help (e.g. some status checks run failed due to internal issue), admin team members will help asap.

@hippy-service
Copy link
Copy Markdown

hippy-service Bot commented May 21, 2026

After a quick scan, I have approved workflow to run.

Details

🏷️ New commits in this PR would not be tested automatically until this pull request is reviewed by our collaborators.
🏷️ No need to worry about the status of merge_guard and [gh] pull request merge guard / merge_guard (pull_request_target) checks, once this pull request is met merge requirements, it will be automatically converted to successful status.

Add diagnostic output to help debug build environment issues
across different CI environments.
@4ek0
Copy link
Copy Markdown
Author

4ek0 commented May 22, 2026

Need help with CI checks #help

@hippy-service hippy-service Bot added the need: help Wanted extra help label May 22, 2026
Copy link
Copy Markdown
Author

@4ek0 4ek0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@4ek0 4ek0 closed this May 22, 2026
@4ek0 4ek0 reopened this May 22, 2026
@hippy-service
Copy link
Copy Markdown

hippy-service Bot commented May 22, 2026

After a quick scan, I have approved workflow to run.

Details

🏷️ New commits in this PR would not be tested automatically until this pull request is reviewed by our collaborators.
🏷️ No need to worry about the status of merge_guard and [gh] pull request merge guard / merge_guard (pull_request_target) checks, once this pull request is met merge requirements, it will be automatically converted to successful status.

@4ek0 4ek0 closed this May 22, 2026
@4ek0 4ek0 reopened this May 22, 2026
@hippy-service
Copy link
Copy Markdown

hippy-service Bot commented May 22, 2026

After a quick scan, I have approved workflow to run.

Details

🏷️ New commits in this PR would not be tested automatically until this pull request is reviewed by our collaborators.
🏷️ No need to worry about the status of merge_guard and [gh] pull request merge guard / merge_guard (pull_request_target) checks, once this pull request is met merge requirements, it will be automatically converted to successful status.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build: gradle driver: js framework: android need: help Wanted extra help size: s Denotes a PR that changes 10-99 lines

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants