Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

When BRANCH is a tag --incremental does not work

See original GitHub issue

Here we go:

$ ./scripts/
projects...... clang;lld
targets....... X86
branch........ llvmorg-9.0.0-rc1
stage1-opts... --build-stage1-only --install-stage1-only
misc-opts..... --incremental
build-dir..... /home/sdi/src/llvm-toolchain/build
install-dir... /home/sdi/src/llvm-toolchain/install

== Checking CC and LD ==

CC: /usr/lib/llvm-9/bin/clang
CXX: /usr/lib/llvm-9/bin/clang++
LD: /usr/bin/ld.lld-9

== Checking dependencies ==


== Updating LLVM ==

Note: checking out 'llvmorg-9.0.0-rc1'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 6aa75a25bdee Merging r367215: ------------------------------------------------------------------------ r367215 | hans | 2019-07-29 11:49:04 +0200 (Mon, 29 Jul 2019) | 66 lines
$ cd tc-build/llvm-project
$ git branch
* (HEAD detached at llvmorg-9.0.0-rc1)

UPDATE: Add correct log in Updating LLVM section

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:6 (6 by maintainers)

github_iconTop GitHub Comments

nathanchancecommented, Aug 6, 2019

Yes, we run git fetch origin which will fetch both new tags and branches. It looks like your example properly checked out. llvmorg-9.0.0-rc1?

nathanchancecommented, Mar 31, 2020

Re-reading this, I think there is some confusion over the meaning of --incremental. --incremental deals with not removing the build artifacts from a previous compile, not incrementally updating the repo. There is no bug here.

Read more comments on GitHub >

github_iconTop Results From Across the Web

[Bug] tag & increment override not working #2851 - GitHub
Hi there, I am new to gitversion and currently trying to setup our CI to integrate with it. But can't really get it...
Read more >
Branch/master tag revision increments using Git - Stack Overflow
The problem is when you add a new tag to an existing branch. Let's say I create a support branch for 1.0 -...
Read more >
How to use GitVersion to get sensible versioning
Since that 1.1.0 tag is not visible from the develop branch, it might come as a surprise that GitVersion still bumped the minor...
Read more >
Migrate a repository incrementally - AWS CodeCommit
Describes how to migrate or push a repository in increments, to avoid potential problems with network connectivity or other issues.
Read more >
How to setup an incremental ROOT building procedure
Note: It should be enough to “cd <branch/specific/builddir>” and then run the “update” procedure (because the already built binaries know where ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found