Closed
Description
From: https://travis-ci.org/GoogleCloudPlatform/google-cloud-python/builds/158529136#L1224-L1232
======================================================================
FAIL: test_analyze_entities (language.TestLanguage)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/home/travis/build/GoogleCloudPlatform/google-cloud-python/system_tests/language.py", line 103, in test_analyze_entities
self._check_analyze_entities_result(entities)
File "/home/travis/build/GoogleCloudPlatform/google-cloud-python/system_tests/language.py", line 77, in _check_analyze_entities_result
self.assertTrue(0.7 < entity1.salience < 0.8)
AssertionError: False is not trueMetadata
Metadata
Assignees
Labels
No labels
Activity
tseaver commentedon Sep 8, 2016
Similar error in
test_anaylze_entities_from_blob:dhermes commentedon Sep 8, 2016
Indeed. Le sigh.
dhermes commentedon Sep 8, 2016
@jgeewax Can you weigh in here? The actual output of the API seems to be a moving target. Note that the input is a simple sentence that hasn't changed:
dhermes commentedon Sep 9, 2016
In the meanwhile I'm going to let this set of tests go green, working on a PR now
Widening the salience range for natural language system tests.
dhermes commentedon Sep 9, 2016
@jgeewax Can you weigh in here?
jgeewax commentedon Sep 16, 2016
I expect that the underlying model used here will evolve and "get better" over time. We should assert that there is a salience that is non-zero -- but how "salient" something is as determined by the algorithm can't be frozen.
If we get back a zero, missing, etc, that means that the API contract is just "broken", but 0.75 today and 0.82 tomorrow doesn't mean our client is busted...
Loosening salience assumptions in language system test.
chore: move samples from python-docs-sample (#45)
bug: updates `__eq__` comparison on TableConstraint (#2274)