git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2019, #07; Fri, 28)
Date: Tue, 02 Jul 2019 13:44:33 -0700	[thread overview]
Message-ID: <xmqqftno2mku.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <xmqqzhm173sp.fsf@gitster-ct.c.googlers.com> (Junio C. Hamano's message of "Fri, 28 Jun 2019 15:17:42 -0700")

Junio C Hamano <gitster@pobox.com> writes:

> * nd/index-dump-in-json (2019-06-26) 11 commits
>  - SQUASH???
>  - t3008: use the new SINGLE_CPU prereq
>  - read-cache.c: dump "IEOT" extension as json
>  - read-cache.c: dump "EOIE" extension as json
>  - resolve-undo.c: dump "REUC" extension as json
>  - fsmonitor.c: dump "FSMN" extension as json
>  - split-index.c: dump "link" extension as json
>  - dir.c: dump "UNTR" extension as json
>  - cache-tree.c: dump "TREE" extension as json
>  - read-cache.c: dump common extension info in json
>  - ls-files: add --json to dump the index
>
>  "ls-files" learned "--debug-json" option to dump the contents and
>  the extensions of the index file.

The t3011 test in this topic seems timing-dependent-flaky.

When we get "not ok 3 - ls-files --json, split index",
the "filtered" one looks like this:

$ diff -U999 t/t3011/split-index filtered
--- t/t3011/split-index	2019-07-02 13:17:19.676719212 -0700
+++ filtered	2019-07-02 13:40:32.068638361 -0700
@@ -1,39 +1,19 @@
 {
   "version": 2,
   "oid": <string>,
   "mtime_sec": <number>,
   "mtime_nsec": <number>,
   "entries": [
-    {
-      "id": 0,
-      "name": "",
-      "mode": "100644",
-      "flags": 0,
-      "oid": <string>,
-      "stat": {
-        "ctime_sec": <number>,
-        "ctime_nsec": <number>,
-        "mtime_sec": <number>,
-        "mtime_nsec": <number>,
-        "device": <number>,
-        "inode": <number>,
-        "uid": <number>,
-        "gid": <number>,
-        "size": 4
-      },
-      "file_offset": <number>
-    }
   ],
   "extensions": {
     "link": {
       "file_offset": <number>,
       "ext_size": <number>,
       "oid": <string>,
       "delete_bitmap": [
       ],
       "replace_bitmap": [
-        0
       ]
     }
   }
 }



  parent reply	other threads:[~2019-07-03  0:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-28 22:17 What's cooking in git.git (Jun 2019, #07; Fri, 28) Junio C Hamano
2019-07-01 13:16 ` ab/no-kwset, was " Johannes Schindelin
2019-07-01 16:39   ` Junio C Hamano
2019-07-01 21:22   ` Ævar Arnfjörð Bjarmason
2019-07-02 12:15     ` Johannes Schindelin
2019-07-01 15:02 ` Rohit Ashiwal
2019-07-01 16:05   ` Junio C Hamano
2019-07-01 15:22 ` Taylor Blau
2019-07-01 16:05   ` Junio C Hamano
2019-07-01 15:36 ` Taylor Blau
2019-07-02 20:44 ` Junio C Hamano [this message]
2019-07-03 11:13   ` Johannes Schindelin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqftno2mku.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=pclouds@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).