sapling/tests/test-fb-hgext-infinitepush-backup-logging.t
Liubov Dmitrieva 6f9fa2f143 infinitepush: do not expose word 'infinitepush' to users and make it clear that all that messages are about autobackup (in background)
Summary:
Make it clear that all that messages are about autobackup (in background)

Even if it is disabled, manual `hg pushbackup` works

Also, since we announced publicly about renaming infinitepush we should not use it in user facing messages.

Also, that commands enable/disable background cloudsync, probably later we should check if cloudsync is enabled and improve messages to be more precise.

Reviewed By: StanislavGlebik

Differential Revision: D7635640

fbshipit-source-id: 2461b1b45e181c6e24b59f707a17f2fd60d4bb0e
2018-04-16 10:35:14 -07:00

29 lines
637 B
Perl

$ . "$TESTDIR/library.sh"
$ . "$TESTDIR/infinitepush/library.sh"
$ setupcommon
Setup server
$ hg init repo
$ cd repo
$ setupserver
$ cd ..
Clone
$ hg clone ssh://user@dummy/repo client -q
$ cd client
Create log dir
$ mkdir $TESTTMP/logs
Setup background backup logging
$ printf "\n[infinitepushbackup]\nlogdir=$TESTTMP/logs" >> .hg/hgrc
$ mkcommit first
Check that logging fails because of wrong permissions
$ hg pushbackup --background
$ waitbgbackup
$ hg pushbackup --background --debug
$TESTTMP/logs directory has incorrect permission, background backup logging will be disabled
$ waitbgbackup