diff options
| author | James Ennis <james.ennis@codethink.co.uk> | 2019-06-06 11:52:00 +0100 |
|---|---|---|
| committer | bst-marge-bot <marge-bot@buildstream.build> | 2019-06-06 13:24:08 +0000 |
| commit | ab9a9b5aa7930c16afad93d077603ade79a41e5c (patch) | |
| tree | 0532163f70581b9119b9f16c20d6ed6745fa4794 /tests/sourcecache | |
| parent | 0b7a9f3e48d1cfcdd16ca01f3b8643a1c1753876 (diff) | |
| download | buildstream-ab9a9b5aa7930c16afad93d077603ade79a41e5c.tar.gz | |
tests/sourcecache/push.py: Less strict initialisation checkjennis/fix_failing_test
When we are testing push failures, we are being too strict
when we try to verify that the remote has failed to be initialized.
The assertion was failing because of slightly different gRPC error
messages. Now the assertion is less strict but still appropriate.
Diffstat (limited to 'tests/sourcecache')
| -rw-r--r-- | tests/sourcecache/push.py | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/tests/sourcecache/push.py b/tests/sourcecache/push.py index abab1616c..065047b1b 100644 --- a/tests/sourcecache/push.py +++ b/tests/sourcecache/push.py @@ -179,8 +179,8 @@ def test_push_fail(cli, tmpdir, datafiles): # build and check that it fails to set up the remote res = cli.run(project=project_dir, args=['build', 'push.bst']) res.assert_success() - assert ("Failed to initialize remote {}: Connect Failed" - .format(remote)) in res.stderr + + assert "Failed to initialize remote {}".format(remote) in res.stderr assert "Pushing" not in res.stderr assert "Pushed" not in res.stderr |