You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Valentyn Tymofieiev (JIRA)" <ji...@apache.org> on 2017/11/29 21:09:00 UTC
[jira] [Commented] (BEAM-3270) Make Perfkit benchmarker logs
available for debugging
[ https://issues.apache.org/jira/browse/BEAM-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16271544#comment-16271544 ]
Valentyn Tymofieiev commented on BEAM-3270:
-------------------------------------------
CC: [~alanmyrvold] [~chamikara]
> Make Perfkit benchmarker logs available for debugging
> -----------------------------------------------------
>
> Key: BEAM-3270
> URL: https://issues.apache.org/jira/browse/BEAM-3270
> Project: Beam
> Issue Type: Improvement
> Components: testing
> Reporter: Valentyn Tymofieiev
> Assignee: Jason Kuster
> Priority: Minor
>
> Logs produced by a failed performance test using Perfkit Benchmarker do not have enough information about the nature of the failure. Looking at what is being printed, the actual logs are stored in /tmp. We should make them available in the test execution logs or attach as artifacts to the Jenkins build. Copying to the workspace may be an option, although workspace may be a subject to cleanup. Example of current log trace:
> test_wordcount_it (apache_beam.examples.wordcount_it_test.WordCountIT) ... /tmp/perfkitbenchmarker/runs/312cddb3/beam/sdks/python/apache_beam/coders/typecoders.py:134: UserWarning: Using fallback coder for typehint: <type 'NoneType'>.
> warnings.warn('Using fallback coder for typehint: %r.' % typehint)
> 2017-11-28 00:15:12,297 312cddb3 MainThread beam_integration_benchmark(1/1) ERROR Error during benchmark beam_integration_benchmark
> Traceback (most recent call last):
> File "/home/jenkins/jenkins-slave/workspace/beam_PerformanceTests_Python/PerfKitBenchmarker/perfkitbenchmarker/pkb.py", line 584, in RunBenchmark
> DoRunPhase(spec, collector, detailed_timer)
> File "/home/jenkins/jenkins-slave/workspace/beam_PerformanceTests_Python/PerfKitBenchmarker/perfkitbenchmarker/pkb.py", line 495, in DoRunPhase
> samples = spec.BenchmarkRun(spec)
> File "/home/jenkins/jenkins-slave/workspace/beam_PerformanceTests_Python/PerfKitBenchmarker/perfkitbenchmarker/linux_benchmarks/beam_integration_benchmark.py", line 159, in Run
> job_type=job_type)
> File "/home/jenkins/jenkins-slave/workspace/beam_PerformanceTests_Python/PerfKitBenchmarker/perfkitbenchmarker/providers/gcp/gcp_dpb_dataflow.py", line 90, in SubmitJob
> assert retcode == 0, "Integration Test Failed."
> AssertionError: Integration Test Failed.
> 2017-11-28 00:15:12,298 312cddb3 MainThread beam_integration_benchmark(1/1) INFO Cleaning up benchmark beam_integration_benchmark
> 2017-11-28 00:15:12,300 312cddb3 MainThread beam_integration_benchmark(1/1) ERROR Benchmark 1/1 beam_integration_benchmark (UID: beam_integration_benchmark0) failed. Execution will continue.
> 2017-11-28 00:15:12,323 312cddb3 MainThread INFO Benchmark run statuses:
> ---------------------------------------------------------------
> Name UID Status
> ---------------------------------------------------------------
> beam_integration_benchmark beam_integration_benchmark0 FAILED
> ---------------------------------------------------------------
> Success rate: 0.00% (0/1)
> 2017-11-28 00:15:12,323 312cddb3 MainThread INFO Complete logs can be found at: /tmp/perfkitbenchmarker/runs/312cddb3/pkb.log
> 2017-11-28 00:15:12,324 312cddb3 MainThread INFO Completion statuses can be found at: /tmp/perfkitbenchmarker/runs/312cddb3/completion_statuses.json
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)