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 Job ID Name Coverage
  Tests
passed #153747
checks-py2

00:03:59

passed #153748
checks-py3

00:05:09

passed #153749
rust-cargo-test-py2

00:01:25

passed #153750
rust-cargo-test-py3

00:02:25

passed #153751
test-py2

00:14:05

passed #153757
test-py2-chg

00:20:54

passed #153753
test-py2-pure

00:20:08

failed #153755
test-py2-rust

00:21:48

passed #153752
test-py3

00:12:35

passed #153758
test-py3-chg

00:08:14

passed #153754
test-py3-pure

00:12:38

passed #153756
test-py3-rust

00:13:20

 
  Phabricator
skipped #153759
phabricator-refresh
 
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