share: move share safe functionality out of experimental

The share-safe functionality is complete and all configuration options are
implemented. The behavior is well discussed on mailing list and in reviews.

Let's unmark this as experimental to solve a chichen and egg issue.

Differential Revision: https://phab.mercurial-scm.org/D9823
13 jobs for topic/default/share-safe-fixes in 21 minutes and 48 seconds (queued for 4 seconds)
Status Name Job ID Coverage
  Tests
passed checks-py2 #153747

00:03:59

passed checks-py3 #153748

00:05:09

passed rust-cargo-test-py2 #153749

00:01:25

passed rust-cargo-test-py3 #153750

00:02:25

passed test-py2 #153751

00:14:05

passed test-py2-chg #153757

00:20:54

passed test-py2-pure #153753

00:20:08

failed test-py2-rust #153755

00:21:48

passed test-py3 #153752

00:12:35

passed test-py3-chg #153758

00:08:14

passed test-py3-pure #153754

00:12:38

passed test-py3-rust #153756

00:13:20

 
  Phabricator
skipped phabricator-refresh #153759
 
Name Stage Failure
failed
test-py2-rust Tests
Skipped test-sparse-fsmonitor.t: skipped
Skipped test-sparse-revlog.t: missing artifact, run "/tmp/mercurial-ci/tests/artifacts/scripts/generate-churning-bundle.py"
Skipped test-verify-repo-operations.py: missing feature: allow slow tests (use --allow-slow-tests)
Failed test-dirs.py: timed out
# Ran 877 tests, 71 skipped, 1 failed.
python hash seed: 535137861
Running after_script
Uploading artifacts for failed job
ERROR: Job failed: exit code 1