Skip to content
New issue

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

FAIL in test_leaks2, test_leaks3 #1

Open
cfarrow opened this issue Feb 20, 2014 · 3 comments · Fixed by #24
Open

FAIL in test_leaks2, test_leaks3 #1

cfarrow opened this issue Feb 20, 2014 · 3 comments · Fixed by #24
Labels
64-bit bug Something isn't working help wanted Extra attention is needed tests enhance or fix tests

Comments

@cfarrow
Copy link
Contributor

cfarrow commented Feb 20, 2014

The test leaks tests fail under 64-bit python.

@cfarrow
Copy link
Contributor Author

cfarrow commented Mar 24, 2014

I'm still seeing this in the PR builder. Reopening.

@junkmd
Copy link
Collaborator

junkmd commented Nov 27, 2022

Those tests are skipped(see #267 and #297).
Bringing back those tests has a different problem than other environment-dependent tests.

We should make this will be related to the issue of memory leaks and their testing.

So, I will leave this issue Open.

@junkmd
Copy link
Collaborator

junkmd commented Nov 27, 2022

from "Clarity of code snippet in docs" #64 by @8day

It would be good if you clarified that GUIDs in this snippet should be completely different by alternating characters. E.g., instead of three xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx it'd be good to have xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx, yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy and zzzzzzzz-zzzz-zzzz-zzzz-zzzzzzzzzzzz.

Of course, there's a sentence below the snippet that states that GUID must be unique ("separate"), but IMO it wouldn't hurt to clarify this in snippet itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
64-bit bug Something isn't working help wanted Extra attention is needed tests enhance or fix tests
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants