We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello,
Rebecca Palmer noticed out that test_serialization in partd version 1.2.0's tests occasionally fail on ppc64el and s390x . ( https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005045 )
=================================== FAILURES =================================== ______________________________ test_serialization ______________________________ def test_serialization(): with partd_server(hostname='localhost') as (p, server): p.append({'x': b'123'}) q = pickle.loads(pickle.dumps(p)) > assert q.get('x') == b'123' E AssertionError: assert b'' == b'123' E Full diff: E - b'123' E + b'' test_zmq.py:114: AssertionError
The full logs are at: https://ci.debian.net/data/autopkgtest/testing/ppc64el/p/partd/18902384/log.gz https://ci.debian.net/data/autopkgtest/testing/s390x/p/partd/16889914/log.gz
That code failure really looks like some kind of race condition.
We were wondering what to do about this test failure.
Stick a brief sleep in between the append and the get? block building on these architectures? Just ignore it?
Environment:
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hello,
Rebecca Palmer noticed out that test_serialization in partd version 1.2.0's tests occasionally fail on ppc64el and s390x . ( https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005045 )
The full logs are at:
https://ci.debian.net/data/autopkgtest/testing/ppc64el/p/partd/18902384/log.gz
https://ci.debian.net/data/autopkgtest/testing/s390x/p/partd/16889914/log.gz
That code failure really looks like some kind of race condition.
We were wondering what to do about this test failure.
Stick a brief sleep in between the append and the get? block building on these architectures? Just ignore it?
Environment:
The text was updated successfully, but these errors were encountered: