[jira] [Work logged] (AVRO-3067) [Python] Potentially flaky timing in test

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AVRO-3067?focusedWorklogId=642419&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-642419 ]

ASF GitHub Bot logged work on AVRO-3067:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 26/Aug/21 15:52
            Start Date: 26/Aug/21 15:52
    Worklog Time Spent: 10m 
      Work Description: RyanSkraba opened a new pull request #1316:
URL: https://github.com/apache/avro/pull/1316


   Make sure you have checked _all_ steps below.
   
   ### Jira
   
   - [X] My PR addresses the following [Avro Jira](https://issues.apache.org/jira/browse/AVRO/) issues and references them in the PR title. For example, "AVRO-1234: My Avro PR"
     - https://issues.apache.org/jira/browse/AVRO-3067
     - In case you are adding a dependency, check if the license complies with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x).
   
   ### Tests
   
   - [X] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason:
   
   ### Commits
   
   - [X] My commits all reference Jira issues in their subject lines. In addition, my commits follow the guidelines from "[How to write a good git commit message](https://chris.beams.io/posts/git-commit/)":
     1. Subject is separated from body by a blank line
     1. Subject is limited to 50 characters (not including Jira issue reference)
     1. Subject does not end with a period
     1. Subject uses the imperative mood ("add", not "adding")
     1. Body wraps at 72 characters
     1. Body explains "what" and "why", not "how"
   
   ### Documentation
   
   - [ ] In case of new functionality, my PR adds documentation that describes how to use it.
     - All the public functions and the classes in the PR contain Javadoc that explain what it does
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@avro.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 642419)
    Remaining Estimate: 0h
            Time Spent: 10m

> [Python] Potentially flaky timing in test
> -----------------------------------------
>
>                 Key: AVRO-3067
>                 URL: https://issues.apache.org/jira/browse/AVRO-3067
>             Project: Apache Avro
>          Issue Type: Task
>            Reporter: Ryan Skraba
>            Assignee: Ryan Skraba
>            Priority: Minor
>             Fix For: 1.11.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Just saw this on Python pypy-3.7 Tests :
> {code}
> py run-test: commands[0] | coverage run -pm unittest discover --buffer --failfast
> F
> ======================================================================
> FAIL: test_minimum_speed (avro.test.test_bench.TestBench)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "/home/runner/work/avro/avro/lang/py/avro/test/test_bench.py", line 57, in test_minimum_speed
>     .format(MAX_WRITE_SECONDS, NUMBER_OF_TESTS))
> AssertionError: 3.111036313999989 not less than 3 : Took longer than 3 second(s) to write the test file with 10000 values.
> {code}
> This might be a performance regression, but it might also just be a busy build system.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)