Jorge Ramos added the comment:
Mmm, I don't find that option documented in the readme of the MSI folder nor in
the help for buildrelease.bat (and also is not intuitive, what does IIRC stand
for?), nevertheless:
It should be no problem if this PR doesn't pass but it should help
Jorge Ramos added the comment:
I want to document a workaround if anyone benefits from it, this would be step
7:
7) This error goes away if you remove the pyconfig.h from the include directory
before the tests end (and of course, after the test distutils).
This is only a workaround and
Change by Jorge Ramos :
--
keywords: +patch, patch, patch
pull_requests: +11193, 11194, 11195
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issu
Change by Jorge Ramos :
--
keywords: +patch, patch
pull_requests: +11193, 11194
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issu
Change by Jorge Ramos :
--
keywords: +patch
pull_requests: +11193
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue35739>
___
___
Py
New submission from Jorge Ramos :
It would be interesting to allow regrtests to output to command line during
testing with PGO enabled. The default behavior is to not display output unless
some fatal error occurs ("quiet" mode).
Making this issue to create a pu
Jorge Ramos added the comment:
E:\RepoGiT\3.7>"E:\RepoGiT\3.7\PCbuild\amd64\python.exe" -u -Wd -E -bb -m test
-v test_httpservers
== CPython 3.7.2+ (heads/3.7:e1259886ab, Jan 13 2019, 19:16:24) [MSC v.1916 64
bit (AMD64)]
== Windows-10-10.0.17763-SP0 little-endian
== cwd: E
Jorge Ramos added the comment:
the output is stored on the file run.txt above
--
___
Python tracker
<https://bugs.python.org/issue35693>
___
___
Python-bug
Change by Jorge Ramos :
--
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue35157>
___
___
Python-bugs-list
Change by Jorge Ramos :
--
stage: needs patch -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue35156>
___
___
Pyth
Change by Jorge Ramos :
--
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue35399>
___
___
Python-bugs-list
Change by Jorge Ramos :
--
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue35400>
___
___
Python-bugs-list
Change by Jorge Ramos :
--
stage: test needed -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue35693>
___
___
Pyth
Jorge Ramos added the comment:
It is true that I worry about failing tests during PGO training because they
stop me from compiling Python -with- PGO. I also got here to report my
experience and problems back to you guys but, if the problems are known, well,
there's nothing much I c
Jorge Ramos added the comment:
Thanks!
About the alternate set of training data, how (where) do I find it? and about
the layouts, can you point me in the right direction as to learn about them,
into what they do? or try to achieve? and how to use them?
Quoting Steve Dower ( https
Jorge Ramos added the comment:
I have realized that results from rt.bat differ from those when running
buildrelease.bat (see example below)
Why do the tests run OK in rt.bat but fail in buildrelase.bat?
To my best understanding, the tests are summoned directly via rt.bat but also
from
Change by Jorge Ramos :
--
versions: +Python 3.6
___
Python tracker
<https://bugs.python.org/issue35693>
___
___
Python-bugs-list mailing list
Unsubscribe:
Jorge Ramos added the comment:
Ok, thank you. Here are my findings:
steps taken:
1) download today's version of 3.7.2 and 3.8.0 alpha 0
2) navigate to tools/msi
3) run build.bat -x64 (to create amd64 folder under pcbuild)
4) navigate to pcbuild
5) run rt.bat -x64 -v test_httpservers
re
Jorge Ramos added the comment:
The thread doesn't display the attachment icon in bugtracker webpage, so I will
copy the output here:
E:\RepoGiT\3.6>PCbuild\rt.bat -x64 -v test_httpservers
Deleting .pyc files ...
0 .pyc deleted
Cleaning _pth files ...
E:\RepoGiT\3.6>"E:\Rep
Jorge Ramos added the comment:
The test failed, the results on attached file!
--
Added file: https://bugs.python.org/file48037/failed.txt
___
Python tracker
<https://bugs.python.org/issue35
Jorge Ramos added the comment:
Got it, i'll get back with the results
--
___
Python tracker
<https://bugs.python.org/issue35693>
___
___
Python-bugs-list m
Jorge Ramos added the comment:
Got it, maybe the warnings should be more explanatory, like this one:
0:06:17 [219/407/1] test_multiprocessing_fork
test_multiprocessing_fork skipped -- fork is not available on Windows
0:06:17 [220/407/1] test_multiprocessing_forkserver
Jorge Ramos added the comment:
Got it (y)
--
___
Python tracker
<https://bugs.python.org/issue35694>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Jorge Ramos :
while running :
0:04:26 [136/407] test_fork1
test_fork1 skipped -- object
has no attribute 'fork'
0:11:56 [384/407/1] test_wait4 -- test_wait3 skipped
test_wait4 skipped -- object
has no attribute 'fork'
see attached file
New submission from Jorge Ramos :
when running some tests where skipped due to missing modules:
0:02:52 [ 86/407] test_crypt
test_crypt skipped -- No module named '_crypt'
0:02:55 [ 93/407] test_dbm_gnu
test_dbm_gnu skipped -- No module named '_gdbm'
0:02:55 [ 9
New submission from Jorge Ramos :
when running test_httpservers fails:
0:04:53 [171/407] test_httpservers
E:\RepoGiT\3.6\lib\socket.py:144: ResourceWarning: unclosed
_socket.socket.__init__(self, family, type, proto, fileno)
E:\RepoGiT\3.6\lib\test\support\__init__.py:1542
Jorge Ramos added the comment:
May I add that this directory exists, maybe before this run tried to create it
and hence not being able to do it as the first post suggested?
--
___
Python tracker
<https://bugs.python.org/issue30
Jorge Ramos added the comment:
I got this error trying to build Python 3.6.7, why is this closed?
Running PGInstrument|x64 interpreter...
E:\RepoGiT\3.6\lib\test\support\__init__.py:1029: RuntimeWarning: tests may
fail, unable to create temp dir:
D:\Users\yorch\AppData\Local\Temp
Change by Jorge Ramos :
--
components: +Build
___
Python tracker
<https://bugs.python.org/issue35399>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Jorge Ramos :
The following command:
Tools\msi\buildrelease.bat -x64
is used to build a 64 bit version (on win_10_64) of python (using visual studio
2017).
The following modules did not build correctly because, presumably, the
corresponding .PGC files could not be
New submission from Jorge Ramos :
As can be seen in the file, the sysconfig test fails when profiling (PGO) this
utility. This is the very same bug as described in issue#35299
https://bugs.python.org/issue35299 but in distutils.
The problem is that when the test for sysconfig runs, it does
New submission from Jorge Ramos :
Build of Python 3.6.7 fails with error
"LGHT0091: Duplicate symbol 'File:include_pyconfig.h' found"
I am using Windows 10 64bit.
Steps to reproduce this error:
1) Install Visual Studio 2017 (With the python development and native dev
Jorge Ramos added the comment:
Ok, thanks! If it helps, here are all the modules that gave me that suggestion:
pythoncore.vcxproj
_testbuffer.vcxproj
_testcapi.vcxproj
_testimportmultiple.vcxproj
select.vcxproj
_overlapped.vcxproj
_elementtree.vcxproj
_decimal.vcxproj
unicodedata.vcxproj
New submission from Jorge Ramos :
When building python 3.6.7 x64 from source I get multiple warnings:
LINK : LNK4281 - "undesirable base address 0x1D11 for x64 image; set base
address above 4GB for best ASLR optimiz
Jorge Ramos added the comment:
Although I appreciate the confidence placed in me, I think I'm not exactly the
most competent person to make changes to such an important project. I know what
-probably- could be improved (from my very narrow point of view) but I don't
even know wh
Jorge Ramos added the comment:
Yes, my last message is a trimmed version of my next to last message (which
itself is a trimmed version of all the verbose of the build, showing just after
the PGO interpreter wakes up). Although, obviously they where run at different
times (one run completed
Jorge Ramos added the comment:
One more thing: point in case #6 does credit a revision IMO. The build_pgo.bat
file does not exist.
--
___
Python tracker
<https://bugs.python.org/issue35
Jorge Ramos added the comment:
Thank you, I think that will suffice. At least guide folks like myself who want
to build from source and with optimizations in the right direction (on which
folder to work on and which commands to issue to the terminal)
Please keep me posted
Jorge Ramos added the comment:
Hi:
Hmm.. but the installation does fail ("PGO run did not succeed (no
python36!*.pgc files) and there is no data to merge"):
*
Total duration: 35 min 2 sec
Tests result:
Jorge Ramos added the comment:
Hello: I followed the same command: PCBuild\build.bat -d -p x64 -r --pgo and in
summary, it found 5 errors (the last part of this messages contains the
PGInstrument|x64 interpreter verbose). I include a number between parenthesis
to show the test number
Jorge Ramos added the comment:
While building 3.6.7. Path set to 3.6.7 working directory
Running PGInstrument|x64 interpreter...
Run tests sequentially
Exception in callback
_ProactorReadPipeTransport._loop_reading(<_OverlappedF...ne, 64, None)>)
handle: )>
Traceback (most recent
New submission from Jorge Ramos :
When testing the builds when PGO is enabled, or by simply running rt.bat, the
following error is (always) issued:
cpython\include\Python.h(8): fatal error C1083: Cannot include: 'pyconfig.h':
No such file or directory
One example of steps take
New submission from Jorge Ramos :
I want to build from source a 3.6 Python, using PGO for windows.
Followed instructions at https://devguide.python.org/setup/ (the original
search from google was "build python from source windows"). From a newbie
perspective there are several proble
43 matches
Mail list logo