Skip to content

Conversation

@dpiparo
Copy link
Member

@dpiparo dpiparo commented Jan 7, 2026

Should shave off 1-2 minutes from every build.

@dpiparo dpiparo requested a review from guitargeek January 7, 2026 07:21
@dpiparo dpiparo self-assigned this Jan 7, 2026
@dpiparo dpiparo added the clean build Ask CI to do non-incremental build on PR label Jan 7, 2026
@github-actions
Copy link

github-actions bot commented Jan 7, 2026

Test Results

    19 files      19 suites   3d 6h 29m 49s ⏱️
 3 767 tests  3 767 ✅ 0 💤 0 ❌
69 646 runs  69 646 ✅ 0 💤 0 ❌

Results for commit 29dbc50.

♻️ This comment has been updated with latest results.

Copy link
Contributor

@guitargeek guitargeek left a comment

Choose a reason for hiding this comment

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

Nice!

@dpiparo dpiparo added in:CI and removed clean build Ask CI to do non-incremental build on PR labels Jan 7, 2026
@dpiparo dpiparo closed this Jan 7, 2026
@dpiparo dpiparo reopened this Jan 7, 2026
@dpiparo dpiparo marked this pull request as ready for review January 7, 2026 13:58
else:
returncode = subprocess_with_log(f"""
git clone --branch {branch} --single-branch {repository} "{targetdir}"
git clone --depth 1 --branch {branch} --single-branch {repository} "{targetdir}"
Copy link
Member

Choose a reason for hiding this comment

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

I ponder if 1 is the right number. If I remember correctly, we need some history to find the merging point between PR and the master in some circumstances.

Copy link
Collaborator

Choose a reason for hiding this comment

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

maybe as a two-step process? If the search fails, then we clone fully?

Copy link
Member Author

Choose a reason for hiding this comment

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

it is indeed what one can see in the incremental builds. I wonder whether it's an optimisation worth the complication in the code...

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants