Skip to content

text/noreply.test.py fails sporadically #110

Description

@Totktonada

Versions:

The second configuration fails less often, but still. So I guess (and hope) that it is irrelevant to #59 and #96.

$ TEST_RUN_TESTS="$(yes noreply | head -n 100)" make test-memcached
# or several times
$ for i in {1..10}; do TEST_RUN_TESTS="$(yes noreply | head -n 100)" make test-memcached || break; echo -e "\n==== $i ====\n"; done

The fail:

[001] text/noreply.test.py                                            [ fail ]
[001] 
[001] Test failed! Result content mismatch:
[001] --- text/noreply.result	Thu Mar 17 03:14:16 2022
[001] +++ var/rejects/text/noreply.reject	Mon Mar 28 20:13:34 2022
[001] @@ -19,8 +19,6 @@
[001]  <<--------------------------------------------------
[001]  get noreply:foo
[001]  >>--------------------------------------------------
[001] -VALUE noreply:foo 0 1
[001] -1
[001]  END
[001]  <<--------------------------------------------------
[001]  set noreply:foo 0 0 1 noreply
[001] 

Got 4 fails of 100 runs on 2.8.2 and less than 1 per 100 on 2.10.0-beta2-206-g63de77fd8.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    code healthImprove code readability, simplify maintenance and so on

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions