Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(1629)

Unified Diff: telemetry/telemetry/internal/story_runner_unittest.py

Issue 2903023002: [Telemetry] Do not have benchmarks validate story name in expectations during runs. (Closed)
Patch Set: [Telemetry] Do not have benchmarks validate story name in expectations during runs. Created 3 years, 7 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: telemetry/telemetry/internal/story_runner_unittest.py
diff --git a/telemetry/telemetry/internal/story_runner_unittest.py b/telemetry/telemetry/internal/story_runner_unittest.py
index 37ef0d18f598d55c5bcf55223814fb45bb384ce2..ec3f9e909296033310716cc6279f42ce7b36b904 100644
--- a/telemetry/telemetry/internal/story_runner_unittest.py
+++ b/telemetry/telemetry/internal/story_runner_unittest.py
@@ -1224,8 +1224,7 @@ class StoryRunnerTest(unittest.TestCase):
try:
options.output_dir = tmp_path
rc = story_runner.RunBenchmark(fake_benchmark, options)
- # The exception from not having a matching name is caught and the return
- # code is set to a failure code.
- self.assertEqual(rc, 255)
+ # Test should return 0 since only error messages are logged.
+ self.assertEqual(rc, 0)
finally:
shutil.rmtree(tmp_path)

Powered by Google App Engine
This is Rietveld 408576698