heptapod-ci: automatically refresh existing phabricator Diff on push
If a changeset have been submitted to Phabricator and a new version is pushed to heptapod, we should refresh the state on Phabricator. If we do not do this, they are a risk of an older version being applied from Phabricator. In this situation content-divergence will be (rightfully) detected by evolution. We only refresh the Diff if the test pass, to avoid updating Phabricator with broken content.
Status | Job ID | Name | Coverage | ||||||
---|---|---|---|---|---|---|---|---|---|
Tests | |||||||||
failed |
#125969
|
checks-py2 |
00:00:58
|
|
|||||
failed |
#125970
|
checks-py3 |
00:01:19
|
|
|||||
failed |
#125971
|
rust-cargo-test-py2 |
00:01:38
|
|
|||||
failed |
#125972
|
rust-cargo-test-py3 |
00:01:22
|
|
|||||
failed |
#125973
|
rust-cargo-test-py3-dirstate-tree |
00:01:34
|
|
|||||
failed |
#125974
|
test-py2 |
00:00:56
|
|
|||||
failed |
#125981
|
test-py2-chg |
00:01:39
|
|
|||||
failed |
#125976
|
test-py2-pure |
00:01:35
|
|
|||||
failed |
#125978
|
test-py2-rust |
00:01:34
|
|
|||||
failed |
#125975
|
test-py3 |
00:01:40
|
|
|||||
failed |
#125977
|
test-py3-pure |
00:01:29
|
|
|||||
failed |
#125979
|
test-py3-rust |
00:01:38
|
|
|||||
failed |
#125980
|
test-py3-rust-dirstate-tree |
00:01:39
|
|
|||||
Phabricator | |||||||||
skipped |
#125982
|
phabricator-refresh |
|
||||||
Name | Stage | Failure | ||
---|---|---|---|---|
failed
|
test-py2-chg | Tests | ||
|
||||
failed
|
test-py3-rust-dirstate-tree | Tests | ||
|
||||
failed
|
test-py3 | Tests | ||
|
||||
failed
|
test-py3-rust | Tests | ||
|
||||
failed
|
rust-cargo-test-py2 | Tests | ||
|
||||
failed
|
test-py2-rust | Tests | ||
|
||||
failed
|
test-py2-pure | Tests | ||
|
||||
failed
|
rust-cargo-test-py3-dirstate-tree | Tests | ||
|
||||
failed
|
test-py3-pure | Tests | ||
|
||||
failed
|
rust-cargo-test-py3 | Tests | ||
|
||||
failed
|
checks-py3 | Tests | ||
|
||||
failed
|
checks-py2 | Tests | ||
|
||||
failed
|
test-py2 | Tests | ||
|