view tests/test-sparse-with-safe-share.t @ 48598:011f5218ff2d

blackbox: add milliseconds to blackbox logs by default

The current second granularity is often not specific enough to
determine whether an hg command is happening before or after some
other event.

Given that starting a process takes on the order of 1ms (well, for
native processes. It's quite a bit more for python processes),
microseconds seems like unnecessary noise.

This also lines up behavior with the rust version, where we already
switched to millisecond precision.

Differential Revision: https://phab.mercurial-scm.org/D12005

Same with share-safe

  $ echo "[format]"         >> $HGRCPATH
  $ echo "use-share-safe = True" >> $HGRCPATH

  $ cd $TESTTMP

  $ hg init myrepo
  $ cd myrepo
  $ cat > .hg/hgrc <<EOF
  > [extensions]
  > sparse=
  > EOF

  $ echo a > show
  $ echo x > hide
  $ hg ci -Aqm 'initial'

Regression test: checks that this command correctly locks the store
before updating the store [requirements] config.

  $ hg up -q 0
  $ hg debugsparse --include 'hide'