Thread (8 messages) flat view 8 messages, 4 authors, 2016-06-15

Re: Be more careful about updating refs

From: Johannes Schindelin <hidden>
Date: 2016-06-15 22:44:06

Possibly related (same subject, not in this thread)

Hi,

On Thu, 17 Jan 2008, Johannes Sixt wrote:
Charles Bailey schrieb:
quoted
On Thu, Jan 17, 2008 at 11:52:23AM +0100, Johannes Sixt wrote:
quoted
I observed the same (on Windows). The reason is that above-mentioned
commit introduces a call to parse_objects(). But by the time that
fast-import calls write_ref_sha1() (and, hence, this new parse_objects())
it has not yet written a pack file, and parse_objects() fails. I don't
have a clue how to fix this short of reverting the commit.
OK, so it's not just Mac OS X, then.  From your description and my
initial poke at the code,  I can't immediately see a good reason why
the test should succeed on Linux, though.
My analysis is not correct. The pack file is present, but it seems to be
incomplete.

The reason is the NO_MMAP build flag. If you compile with
NO_MMAP=YesPlease on Linux, t9301 fails as well. Does this ring a bell?
Just a wild guess... Could it be that the mmap() happened before contents 
were written to that fd?  The faked mmap() is just a malloc() && pread(), 
and would thus miss out on changes written after the mmap() call.

Ciao,
Dscho
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help