[BEAM-7347] beam_Performance failed with benchmark flag config error

• Type: Bug
• Status: Resolved
• Priority: P1
• Resolution: Fixed
• Fix Version/s: Not applicable
• Component/s: test-failures
• Assignee: Unassigned
• Reporter: Mark Liu
• Created: 17/May/19 01:09
• Updated: 24/Jul/20 19:58
• Resolved: 07/Jun/19 21:06

Description

All performance benchmarks are affected.

Error log from latest beam_PerformanceTests_TextIOIT run:

00:00:24.372 2019-05-17 00:21:24,724 5d6e9583 MainThread beam_integration_benchmark(1/1) ERROR    Error during benchmark beam_integration_benchmark
00:00:24.372 Traceback (most recent call last):
00:00:24.372   File "/home/jenkins/jenkins-slave/workspace/beam_PerformanceTests_TextIOIT/PerfKitBenchmarker/perfkitbenchmarker/pkb.py", line 752, in RunBenchmark
00:00:24.372     DoProvisionPhase(spec, detailed_timer)
00:00:24.372   File "/home/jenkins/jenkins-slave/workspace/beam_PerformanceTests_TextIOIT/PerfKitBenchmarker/perfkitbenchmarker/pkb.py", line 538, in DoProvisionPhase
00:00:24.372     spec.ConstructDpbService()
00:00:24.372   File "/home/jenkins/jenkins-slave/workspace/beam_PerformanceTests_TextIOIT/PerfKitBenchmarker/perfkitbenchmarker/benchmark_spec.py", line 209, in ConstructDpbService
00:00:24.372     self.dpb_service = dpb_service_class(self.config.dpb_service)
00:00:24.372   File "/home/jenkins/jenkins-slave/workspace/beam_PerformanceTests_TextIOIT/PerfKitBenchmarker/perfkitbenchmarker/providers/gcp/gcp_dpb_dataflow.py", line 53, in __init__
00:00:24.372     super(GcpDpbDataflow, self).__init__(dpb_service_spec)
00:00:24.372   File "/home/jenkins/jenkins-slave/workspace/beam_PerformanceTests_TextIOIT/PerfKitBenchmarker/perfkitbenchmarker/dpb_service.py", line 127, in __init__
00:00:24.372     'The flag dpb_service_zone must be provided, for provisioning.')
00:00:24.372 InvalidFlagConfigurationError: The flag dpb_service_zone must be provided, for provisioning.

Seems certain change on PerfkitBenchmarker breaks our beam_integration_benchmark. However, we may be able to have a quick fix on Beam side.

Issue Links

• links to: GitHub Pull Request #8602