New submission from Pablo Galindo Salgado :
The test `test_multiprocessing_spawn` is leaking memory according to the x86
Gentoo Refleaks 3.x buildbot:
x86 Gentoo Refleaks 3.x
http://buildbot.python.org/all/#/builders/1/builds/253
test_multiprocessing_spawn leaked [1, 2, 1] memory blocks
Change by Pablo Galindo Salgado :
--
pull_requests: +7298
___
Python tracker
<https://bugs.python.org/issue33630>
___
___
Python-bugs-list mailing list
Unsub
Pablo Galindo Salgado added the comment:
Serhiy commented in the PR:
>__GLIBC__ and __GLIBC_MINOR__ give you the version of glibc used at >compile
>time. But can not the different version be dynamically linked at >run time?
Should we use the list approach always to avoid proble
Pablo Galindo Salgado added the comment:
Could you make a PR correcting this bug? If you cannot I can do it instead. :)
--
nosy: +pablogsal
___
Python tracker
<https://bugs.python.org/issue33
Change by Pablo Galindo Salgado :
--
nosy: +pablogsal
___
Python tracker
<https://bugs.python.org/issue33829>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Pablo Galindo Salgado :
--
title: example output error -> Error in the output of one example in the
httplib docs
___
Python tracker
<https://bugs.python.org/issu
Pablo Galindo Salgado added the comment:
Python++: Sorry, I still cannot understand exactly what is wrong. Could you
please redact a little paragraph explaining (1) what function/functions are you
using (and maybe a very short example), (2) what is not working and (3) what do
you expect to
Pablo Galindo Salgado added the comment:
I think this should be something that is not included in argparse itself. I can
imagine a scenario in which the manpage is accessible through `./python foo.py
--manpage` but the manpage is not installed systemwide. This will be very
confusing for
Pablo Galindo Salgado added the comment:
>What would cause that confusion? This is not something that would
>change how ‘argparse’ parses its arguments, so I don't know what
>you're referring to.
The (possible) confusion is the existence of a manpage only available though
Pablo Galindo Salgado added the comment:
Since dictionaries are ordered "ordered dictionary" can be a synonym of
"dictionary" and "OrderDict", right?
--
nosy: +pablogsal
___
Python tracker
<h
Pablo Galindo Salgado added the comment:
Well, technically a function can say that it returns a dictionary and this
dictionary will be ordered in 3.6> but is not important for the function return
value. If a function says that it returns a "ordered dictionary" I now (1) that
Pablo Galindo Salgado added the comment:
As I commented on GitHub, it seems that the race in the test (problem covered
in PR7663) disappears once the memory problem is fixed (PR33630). As is a race
condition I am not sure that this affirmation is true, but running 3 test
suites in parallel
Pablo Galindo Salgado added the comment:
I have updated PR7685 to use the temporary list as per Serhiy comments.
--
___
Python tracker
<https://bugs.python.org/issue33
Pablo Galindo Salgado added the comment:
Just for clarification. My question in the PR was:
>I think these are not the only occurrences of method referring to a
>magic method. A quick grep reveals that there are more places where the
>construction the __something__ method happens.
Pablo Galindo Salgado added the comment:
I can reproduce the issue on a i686 GNU/Linux Debian system:
>>> import os
>>> f = open('/tmp/temp', 'wb')
>>> l = os.writev(f.fileno(), [b'x' * 2**16] * 2**15)
Traceback (most recent cal
Pablo Galindo Salgado added the comment:
Docs for sendfile in macOS:
https://www.unix.com/man-page/osx/2/sendfile/
--
___
Python tracker
<https://bugs.python.org/issue33
Pablo Galindo Salgado added the comment:
I cannot reproduce this in 3.6.5:
>>>import sys
>>>import gc
>>>a = type(sys)('a')
>>>b = a.__dict__
>>>print(b['__name__'] is None)
False
>>>del a
>>>gc.collect()
>
Change by Pablo Galindo Salgado :
--
components: +Library (Lib)
versions: +Python 3.8
___
Python tracker
<https://bugs.python.org/issue33870>
___
___
Python-bug
Pablo Galindo Salgado added the comment:
It seems that it was this commit:
https://github.com/python/cpython/commit/5619ab2db3a6c62ffaa55e8826cf67b7459fc484
--
___
Python tracker
<https://bugs.python.org/issue33
Pablo Galindo Salgado added the comment:
And this PR:
https://github.com/python/cpython/pull/698
--
___
Python tracker
<https://bugs.python.org/issue33
Pablo Galindo Salgado added the comment:
test_gdb is failing on the following buildbots:
x86 Gentoo Non-Debug
http://buildbot.python.org/all/#builders/99/builds/1095
AMD64 Debian PGO 3.x
http://buildbot.python.org/all/#builders/47/builds/1173
Gentoo Non-Debug with X 3.7
http
Change by Pablo Galindo Salgado :
--
Removed message: https://bugs.python.org/msg319670
___
Python tracker
<https://bugs.python.org/issue32962>
___
___
Python-bug
New submission from Pablo Galindo Salgado :
I am not sure is a problem we can do something about but right know if you run
the refleak tests with low repetitions it reports leaks:
./python -m test test_list -R 1:1
Run tests sequentially
0:00:00 load avg: 0.66 [1/1] test_list
beginning 2
Change by Pablo Galindo Salgado :
--
title: False positives when running refleaks tests with -R 1:1 -> False
positives when running leak tests with -R 1:1
___
Python tracker
<https://bugs.python.org/issu
Pablo Galindo Salgado added the comment:
Let's make the buildbots happier!
--
___
Python tracker
<https://bugs.python.org/issue33873>
___
___
Python-bugs-l
Change by Pablo Galindo Salgado :
--
keywords: +patch
pull_requests: +7346
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issu
Change by Pablo Galindo Salgado :
--
pull_requests: +7347
___
Python tracker
<https://bugs.python.org/issue33873>
___
___
Python-bugs-list mailing list
Unsub
Pablo Galindo Salgado added the comment:
Updated PR7735 with the checks for invalid parameters.
--
___
Python tracker
<https://bugs.python.org/issue33
Pablo Galindo Salgado added the comment:
What about:
"If tempdir is unset or None (the default value has not been modified) ..."
?
--
nosy: +pablogsal
___
Python tracker
<https://bugs.python.o
Change by Pablo Galindo Salgado :
--
assignee: -> pablogsal
nosy: +pablogsal
___
Python tracker
<https://bugs.python.org/issue31463>
___
___
Python-bugs-lis
Change by Pablo Galindo Salgado :
--
assignee: -> pablogsal
nosy: +pablogsal
___
Python tracker
<https://bugs.python.org/issue33613>
___
___
Python-bugs-lis
Change by Pablo Galindo Salgado :
--
Removed message: https://bugs.python.org/msg320061
___
Python tracker
<https://bugs.python.org/issue33613>
___
___
Python-bug
Pablo Galindo Salgado added the comment:
I would like to work on this issue and on issue31463
--
___
Python tracker
<https://bugs.python.org/issue33613>
___
___
Pablo Galindo Salgado added the comment:
I would like to work on this issue and on bpo31463
--
___
Python tracker
<https://bugs.python.org/issue33613>
___
___
Pablo Galindo Salgado added the comment:
I would like to work on this issue
--
___
Python tracker
<https://bugs.python.org/issue31463>
___
___
Python-bugs-list m
Change by Pablo Galindo Salgado :
--
keywords: +patch
pull_requests: +7436
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issu
Pablo Galindo Salgado added the comment:
There are two problems in test_semaphore_tracker_sigint. One of the problems is
that if `should_die` is False, the code does not check
that no warning is raised (and the warning is being raised, so this
the error has pass silently.) The other problem
Pablo Galindo Salgado added the comment:
I think commit4ffe9c2b251f6e027b26250b7a2618e78d4edd22 from bpo-33718 should be
backported IMO:
bpo-33718: regrtest: use format_duration() to display failed tests (GH-7686)
https://github.com/python/cpython/commit
Pablo Galindo Salgado added the comment:
New changeset 3ad8decd76c736f393755537aeb19b5612c21761 by Pablo Galindo in
branch 'master':
bpo-33716, test_concurrent_futures: increase timeout (GH-7828)
https://github.com/python/cpython/commit/3ad8decd76c736f393755537aeb19b
Change by Pablo Galindo Salgado :
--
keywords: +patch
pull_requests: +7461
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issu
Pablo Galindo Salgado added the comment:
The current status of json.tool also leaks a file descriptor if you use the
same filename or an invalid one (needs debug build to receive this error
message):
$ ./python -m json.tool invalid_file.dat nofile.dat
Expecting value: line 1 column 1 (char
Pablo Galindo Salgado added the comment:
@Rémi can you include a NEWS entry?
Also, indicate that your patch prevents a file descriptor to be leaked in the
cases indicated in my last message.
--
___
Python tracker
<https://bugs.python.
Pablo Galindo Salgado added the comment:
Maybe we should include a test that checks that if you provide an invalid file
the file descriptors are not leaked (it can be in a different PR, maybe).
--
___
Python tracker
<https://bugs.python.
Pablo Galindo Salgado added the comment:
@taleinat Sadly, if the semaphore_tracker receives an invalid command, it
raises and dies, making the test impossible:
cmd, name = line.strip().split(b':')
if cmd ==
Pablo Galindo Salgado added the comment:
Sorry, I was wrong, it does not die. I am investigating this solution using
stderr.
--
___
Python tracker
<https://bugs.python.org/issue33
Pablo Galindo Salgado added the comment:
Additionally, as I commented in the PR, apart from the race condition I think
the test should be modified so it fails if the warning is raised and not
expected:
>The problem is that the test was silently failing when SIGINT was >being
>del
Pablo Galindo Salgado added the comment:
@pitrou I think that should be ideal. The reason is that if we send an invalid
command the cache is not cleared and the semaphore tracker will warn when the
process finishes which is precisely what the test is avoiding
Pablo Galindo Salgado added the comment:
I have updated the PR implementing a PONG command in the semaphore and updating
the test. I have tested on the failing buildbots (gcc110.fsffrance.org) and it
works. Notice that a new pipe for the child to write was needed as the child is
Pablo Galindo Salgado added the comment:
The process seems to use its own stderr and it cannot be captured from the
parent without modifying it AFAIK.
--
___
Python tracker
<https://bugs.python.org/issue33
Pablo Galindo Salgado added the comment:
I have modified the PR to avoid creating an extra pipe in the tracker (the pipe
is created as part of the test). To allow testing with the -R option:
./python -m test test_multiprocessing_fork -v -m test_semaphore_tracker_sigint
-R 3:3
I had to
Pablo Galindo Salgado added the comment:
New changeset 58ed7307ea0b5c5aa052291ebc3030f314f938d8 by Pablo Galindo in
branch 'master':
bpo-33873: Fix bug in `runtest.py` and add checks for invalid `-R` parameters
(GH-7735)
https://github.com/python/cpyt
Change by Pablo Galindo Salgado :
--
nosy: +pablogsal
___
Python tracker
<https://bugs.python.org/issue33990>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Pablo Galindo Salgado :
test_gdb is currently failing on the following buildbots:
http://buildbot.python.org/all/#/builders/54/builds/465
http://buildbot.python.org/all/#/builders/66/builds/178
http://buildbot.python.org/all/#/builders/16/builds/1279
http
Pablo Galindo Salgado added the comment:
I can use
opera -remote "openURL(https://google.com,new-window)"
without problems as per the opera documentation with the latest version:
$opera --version
53.0.2907.110
--
nosy: +pablogsal
Pablo Galindo Salgado added the comment:
What error do you get and what opera version are you using?
--
___
Python tracker
<https://bugs.python.org/issue34
Pablo Galindo Salgado added the comment:
Sorry, you are right! It seems that my Opera opened another tab with Google by
default and I was confused by that. Thanks for the context.
--
___
Python tracker
<https://bugs.python.org/issue34
Pablo Galindo Salgado added the comment:
New changeset 3cf1f154edb88c108877729ea09f4ac174697fea by Pablo Galindo (Bumsik
Kim) in branch 'master':
bpo-34019: Fix wrong arguments for Opera Browser (#8047)
https://github.com/python/cpython/commit/3cf1f154edb88c108877729ea09f4a
New submission from Pablo Galindo Salgado :
In /Lib/test/test_urllib2_localnet.py there is an incorrect usage of
unittest.TestCase (an extra comma makes it use two arguments instead of one):
class BasicAuthTests(unittest.TestCase):
...
def test_basic_auth_success(self
Pablo Galindo Salgado added the comment:
In /Lib/test/test_urllib2_localnet.py there is an incorrect usage of
unittest.TestCase.fail (an extra comma makes it use two arguments instead of
one):
class BasicAuthTests(unittest.TestCase):
...
def test_basic_auth_success(self
Change by Pablo Galindo Salgado :
--
Removed message: https://bugs.python.org/msg320975
___
Python tracker
<https://bugs.python.org/issue34031>
___
___
Python-bug
Change by Pablo Galindo Salgado :
--
keywords: +easy
title: Incorrect usage of unittest.TestCase in test_urllib2_localnet -> [EASY]
Incorrect usage of unittest.TestCase in test_urllib2_localnet
___
Python tracker
<https://bugs.pyth
Change by Pablo Galindo Salgado :
--
versions: -Python 3.4, Python 3.5
___
Python tracker
<https://bugs.python.org/issue34031>
___
___
Python-bugs-list mailin
Pablo Galindo Salgado added the comment:
We have some similar failures on the x86 Gentoo Refleaks 3.7 buildbots:
http://buildbot.python.org/all/#/builders/114/builds/157/steps/4/logs/stdio
http://buildbot.python.org/all/#/builders/114/builds/155/steps/4/logs/stdio
Pablo Galindo Salgado added the comment:
I ran git bisect with @Serhiy reproducer and it yielded commit
3929499914d47365ae744df312e16da8955c90ac as the first bad commit that has this
problem. I did not look more into that but the bisect is reproducible (yields
the same commit if you run it
Change by Pablo Galindo Salgado :
--
Removed message: https://bugs.python.org/msg32
___
Python tracker
<https://bugs.python.org/issue27400>
___
___
Python-bug
Change by Pablo Galindo Salgado :
--
Removed message: https://bugs.python.org/msg321110
___
Python tracker
<https://bugs.python.org/issue27400>
___
___
Python-bug
Pablo Galindo Salgado added the comment:
I investigated that commit but I cannot find anything :(.
--
___
Python tracker
<https://bugs.python.org/issue34
Pablo Galindo Salgado added the comment:
I think I found it. After doing the bisect manually (as redirecting
stdout/stderr) seems to affect somehow the test) I found commit
b0a7a037b8fde56b62f886d5188bced7776777b4 as the culprit. Reverting this commit
on the current master seem to solve the
Pablo Galindo Salgado added the comment:
@Antoine Wow, it seems that we both
foundb0a7a037b8fde56b62f886d5188bced7776777b4 with one minute of difference :D
I added Yuri to the noise list as is the author of that PR.
--
___
Python tracker
<ht
Change by Pablo Galindo Salgado :
--
pull_requests: +7707
___
Python tracker
<https://bugs.python.org/issue34019>
___
___
Python-bugs-list mailing list
Unsub
Pablo Galindo Salgado added the comment:
New changeset 8902a1d14e9fe6fb80f4145ad4ea27a579567289 by Pablo Galindo in
branch '2.7':
[2.7] bpo-34019: Fix wrong arguments for Opera Browser (GH-8047) (#8126)
https://github.com/python/cpython/commit/8902a1d14e9fe6fb80f4145ad4ea27
Pablo Galindo Salgado added the comment:
This behaviour also happens on the current master.
--
nosy: +pablogsal
___
Python tracker
<https://bugs.python.org/issue34
Change by Pablo Galindo Salgado :
--
versions: +Python 3.6, Python 3.7, Python 3.8
___
Python tracker
<https://bugs.python.org/issue34110>
___
___
Python-bug
Pablo Galindo Salgado added the comment:
It seems that this buildbot failure is related to this issue:
https://buildbot.python.org/all/#/builders/105/builds/192
1 test failed:
test_regrtest
43 tests skipped:
test_aepack test_al test_applesingle test_bsddb185 test_bsddb3
test_cd
New submission from Pablo Galindo Salgado :
The x86 Gentoo Refleaks 3.x report that test_sys_setprofile is potentially
leaking referenecs:
https://buildbot.python.org/all/#/builders/1/builds/292
--
Ran 21 tests in 0.007s
OK
Pablo Galindo Salgado added the comment:
Same error in the x86 Gentoo Refleaks 3.7 buildbot:
https://buildbot.python.org/all/#/builders/114/builds/174
--
___
Python tracker
<https://bugs.python.org/issue34
Pablo Galindo Salgado added the comment:
Another failure in sx86 Windows XP VS9.0 2.7:
https://buildbot.python.org/all/#/builders/105/builds/195
Total duration: 28 min 12 sec
Tests result: FAILURE then FAILURE
test test_regrtest failed -- Traceback (most recent call last):
File
"d:\c
New submission from Pablo Galindo Salgado :
test_cmd_line test_utf8_mode test_warnings fail in AMD64 FreeBSD CURRENT
buildbots:
https://buildbot.python.org/all/#/builders/79/builds/186
https://buildbot.python.org/all/#/builders/60/builds/182
Sample error:
test_xoptions
New submission from Pablo Galindo Salgado :
Builder x86 Gentoo Refleaks 3.x reports that test_xml_etree_c is potentially
leaking references and blocks:
https://buildbot.python.org/all/#builders/1/builds/295
--
Ran 148 tests
Change by Pablo Galindo Salgado :
--
nosy: +pablogsal
___
Python tracker
<https://bugs.python.org/issue34227>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Pablo Galindo Salgado :
The Gentoo Refleaks 3.7 buildbot is reporting that test_smtplib may be leaving
with dangling threads:
https://buildbot.python.org/all/#builders/114/builds/179
FAILED (errors=7)
Warning -- threading._dangling was modified by test_smtplib
Before
Pablo Galindo Salgado added the comment:
New failure on AMD64 Windows8.1 Refleaks 3.6:
https://buildbot.python.org/all/#builders/64/builds/301
--
___
Python tracker
<https://bugs.python.org/issue34
Pablo Galindo Salgado added the comment:
I think it may be something extra as
test_send_message_error_on_non_ascii_addrs_if_no_smtputf8 is failing when you
run the test with -R:
./python -W error -m test test_smtplib -R 3:3
Warning -- threading._dangling was modified by test_smtplib
Pablo Galindo Salgado added the comment:
The TypeError is because the test is misusing the assertRaises API:
self.assertRaises(smtplib.SMTPNotSupportedError,
smtp.send_message(msg))
should be
self.assertRaises(smtplib.SMTPNotSupportedError
Pablo Galindo Salgado added the comment:
That was from commit 48ed88a93bb0bbeaae9a4cfaa533e4edf13bcb51
--
___
Python tracker
<https://bugs.python.org/issue34
Pablo Galindo Salgado added the comment:
Oh, sorry, my bad. That was precisely what commit
48ed88a93bb0bbeaae9a4cfaa533e4edf13bcb51 changed. The problem with running with
-R still happens:
==
ERROR
New submission from Pablo Galindo Salgado :
Test compile is hanging or failing in AMD(64) Ubuntu buildbots. For example:
https://buildbot.python.org/all/#/builders/157/builds/77
https://buildbot.python.org/all/#/builders/154/builds/90
Example errors:
running: test_tools (3 min 49 sec
Change by Pablo Galindo Salgado :
--
title: test_compile is hanging im AMD Ubuntu buildbots -> test_compile hangs in
AMD Ubuntu buildbots
___
Python tracker
<https://bugs.python.org/issu
Pablo Galindo Salgado added the comment:
New failure on s390x SLES 3.7:
https://buildbot.python.org/all/#/builders/122/builds/540
--
___
Python tracker
<https://bugs.python.org/issue34
Pablo Galindo Salgado added the comment:
New failure on x86 Windows7 3.x:
https://buildbot.python.org/all/#/builders/58/builds/1174
test_timeout (test.test_multiprocessing_spawn.WithThreadsTestSemaphore) ...
skipped 'test not appropriate for threads'
test test_multiprocessing_sp
Pablo Galindo Salgado added the comment:
New failure on AMD64 Ubuntu 3.x:
https://buildbot.python.org/all/#/builders/154/builds/100
test_single_statement (test.test_compile.TestSpecifics) ... ok
Timeout (0:15:00)!
Thread 0x7f30435d3080 (most recent call first):
File
"/home/bui
Pablo Galindo Salgado added the comment:
This error is happening in the x86-64 High Sierra 3.7 buildbot:
https://buildbot.python.org/all/#/builders/147/builds/174
==
FAIL: test_startup_imports
Change by Pablo Galindo Salgado :
--
status: closed -> open
___
Python tracker
<https://bugs.python.org/issue34177>
___
___
Python-bugs-list mailing list
Un
New submission from Pablo Galindo Salgado :
Some tests in test_socket and test_asyncio are receiving timeouts in AMD64
Windows10 3.x buildbots:
test_asyncio: https://buildbot.python.org/all/#/builders/3/builds/1192
test_socket: https://buildbot.python.org/all/#/builders/3/builds/1191
Sample
Change by Pablo Galindo Salgado :
--
title: test_socket timeouts in AMD64 Windows10 3.x buildbots -> test_socket and
test_asyncio timeouts in AMD64 Windows10 3.x buildbots
___
Python tracker
<https://bugs.python.org/issu
Pablo Galindo Salgado added the comment:
Is possible that this are two separate issues.
--
___
Python tracker
<https://bugs.python.org/issue34316>
___
___
Pytho
Pablo Galindo Salgado added the comment:
New failure on AMD64 Ubuntu 3.7:
test_single_statement (test.test_compile.TestSpecifics) ... ok
Timeout (0:15:00)!
Thread 0x7f5f41d9e080 (most recent call first):
File
"/home/buildbot/buildarea/3.7.einat-ubuntu/build/Lib/test/test_compi
New submission from Pablo Galindo Salgado :
test_zipfile gets OverflowError in multiple buildbots:
https://buildbot.python.org/all/#/builders/106/builds/1374
https://buildbot.python.org/all/#/builders/106/builds/1375
https://buildbot.python.org/all/#/builders/106/builds/1376
Example error log
Pablo Galindo Salgado added the comment:
More failures on x86 Gentoo Installed with X 3.x:
https://buildbot.python.org/all/#/builders/103/builds/1240
https://buildbot.python.org/all/#/builders/103/builds/1241
https://buildbot.python.org/all/#/builders/103/builds/1242
New submission from Pablo Galindo Salgado :
test_subprocess.POSIXProcessTestCase fails in AMD64 Ubuntu 3.x buildbots:
https://buildbot.python.org/all/#/builders/154/builds/104
It seems that it has some problems with (unclosed?) file descriptors:
test_terminate_dead
4201 - 4300 of 4566 matches
Mail list logo
