a.foulon@xxxxxxxxx wrote on Mon, 05 Nov 2012 02:02 -0800:
> Hi,
>
> Here is my import :
>
> Importing from //depot@all into XXXXX
> Initialized empty Git repository in
> /home/arthur/projets_git/XXXXX/XXXXX/.git/
> Importing revision 4258 (43%)
> Importing new branch depot/DEV_DATA
>
> Resuming with change 4258
> Importing revision 5828 (63%)
> Importing new branch depot/RELEASE_1.0
>
> Resuming with change 5828
> Importing revision 7720 (88%)
> Importing new branch depot/RELEASE_1.0.0
>
> Resuming with change 7720
> Importing revision 8588 (100%)
> Updated branches: DEV_DATA RELEASE_1.0 MAINLINE/02_SubSystem/10_ARINC_429
> MAINLINE RELEASE_1.0.0
> fast-import failed: error: unable to resolve reference
> refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429: Not a directory
> error: Unable to lock
> refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429
> error: unable to resolve reference
> refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429: Not a directory
> error: Unable to lock
> refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429
> error: unable to resolve reference
> refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429: Not a directory
> error: Unable to lock
> refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429
> error: unable to resolve reference
> refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429: Not a directory
> error: Unable to lock
> refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429
> error: unable to resolve reference
> refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429: Not a directory
> error: Unable to lock
> refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429
> error: unable to resolve reference
> refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429: Not a directory
> error: Unable to lock
> refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429
> error: unable to resolve reference
> refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429: Not a directory
> error: Unable to lock
> refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429
> git-fast-import statistics:
> ---------------------------------------------------------------------
> Alloc'd objects: 170000
> Total objects: 169644 ( 195421 duplicates )
> blobs : 92182 ( 186294 duplicates 74565 deltas)
> trees : 70889 ( 9127 duplicates 57686 deltas)
> commits: 6573 ( 0 duplicates 0 deltas)
> tags : 0 ( 0 duplicates 0 deltas)
> Total branches: 8 ( 8 loads )
> marks: 1024 ( 0 unique )
> atoms: 19603
> Memory total: 19217 KiB
> pools: 12576 KiB
> objects: 6640 KiB
> ---------------------------------------------------------------------
> pack_report: getpagesize() = 4096
> pack_report: core.packedGitWindowSize = 33554432
> pack_report: core.packedGitLimit = 268435456
> pack_report: pack_used_ctr = 19803
> pack_report: pack_mmap_calls = 65
> pack_report: pack_open_windows = 10 / 11
> pack_report: pack_mapped = 257715823 / 268009874
> ---------------------------------------------------------------------
>
>
> Import crash after importing revision, my import have not files
Thanks, that is interesting output.
Adding Vitor who knows his way around the branch detection
code. The first mail by Arthur is here, which focuses more
on the backtrace from "p4 describe" errors, but also suggests
something is dodgy in branch detection:
http://thread.gmane.org/gmane.comp.version-control.git/208693
I'm not sure if this is a --verbose run, though, as I don't see
any chatter like "branch is xxx". So I'm not sure if the
auto-parent detection code got run.
The "unable to resolve reference" comes from refs.c, which is
when fast-import calls update_branch() on each of the changed
branches as it is finishing.
Vitor, what could git-p4 have done to create a branch name called
"refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429"?
Any other questions for Arthur?
-- Pete
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html