GeezerVison is showing github.com — gh-100238: Use setuptools in peg-generator and reenable tests by lysnikolaou · Pull Request #104798 · python/cpython
Conversation
lysnikolaou
commented
May 23, 2023
•
edited by bedevere-bot
Loading
Uh oh!
There was an error while loading. Please reload this page.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
@lysnikolaou you need to probably rebase the changes in the PR that removes the endings from lines (also two windows tests are failing).
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
We still have the failing windows tests. This may be something regarding the name of the binary perhaps?
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
It appears so and I'm not sure why. The only other test that uses this (test_cppext) is skipped on Windows, so we don't really have something to compare.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
It appears so and I'm not sure why
Do you know if python_d.exe is correct on Windows? I think that otherwise this line is kind of wrong:
Run: D:\a\cpython\cpython\PCbuild\win32\python_d.exe -X dev -m venv venv
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
pablogsal
commented
May 25, 2023
•
edited
Loading
Uh oh!
There was an error while loading. Please reload this page.
|
Also that looks odd because there should be a temporary directory there no (as in /tmp/.../venv)?
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Also that looks odd because there should be a temporary directory there no (as in /tmp/.../venv)?
That's okay, since that's the command that creates the venv.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
Probabaly no backport for this, right?
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Probabaly no backport for this, right?
I don't think so, but I also don't think it would hurt
|
lysnikolaou reacted with thumbs up emoji
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
This was referenced May 26, 2023
|
@pablogsal I built #105056 on top. I think it would be reasonable to backport this to 3.12, so I can backport mine as is. WDYT?
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
Thanks @lysnikolaou for the PR 🌮🎉.. I'm working now to backport this PR to: 3.12.
🐍🍒⛏🤖
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
I've asked Petr to label this with the 3.12 label so we know the CI results before a decision is made.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
(I pushed the button to open the 3.12 PR for Miro; I'm not implying it should be merged.)
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
I'm okay with backporting, since this is just re-enabling a test, so it really wouldn't hurt. I'll leave it up to @pablogsal though.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
I'm okay with backporting, since this is just re-enabling a test, so it really wouldn't hurt. I'll leave it up to @pablogsal though.
The problem with the back port is that we have ref leaks with this PR on main no? If we back port without fixing them we are going to have them also on 3.12
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
I'm okay with backporting, since this is just re-enabling a test, so it really wouldn't hurt. I'll leave it up to @pablogsal though.
The problem with the back port is that we have ref leaks with this PR on main no? If we back port without fixing them we are going to have them also on 3.12
That's right, I meant after fixing the refleaks.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
I'm okay with backporting, since this is just re-enabling a test, so it really wouldn't hurt. I'll leave it up to @pablogsal though.
The problem with the back port is that we have ref leaks with this PR on main no? If we back port without fixing them we are going to have them also on 3.12
That's right, I meant after fixing the refleaks.
In that case I am ok back porting 👍
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
erlend-aasland
added a commit
to erlend-aasland/cpython
that referenced
this pull request
Jun 23, 2023
Since pythongh-104798 (Use setuptools in peg-generator and reenable
tests), the TestCParser test case has been producing ref leaks.
erlend-aasland
added a commit
that referenced
this pull request
Jun 23, 2023
…6024)
Since gh-104798 (Use setuptools in peg-generator and reenable
tests), the TestCParser test case has been producing ref leaks.
⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️
Hi! The buildbot AMD64 Windows11 Bigmem 3.12 has failed when building commit 6371029.
What do you need to do:
- Don't panic.
- Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
- Go to the page of the buildbot that failed (https://buildbot.python.org/all/#builders/1117/builds/131) and take a look at the build logs.
- Check if the failure is related to this commit (6371029) or if it is a false positive.
- If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.
You can take a look at the buildbot page here:
https://buildbot.python.org/all/#builders/1117/builds/131
Summary of the results of the build (if available):
== Tests result: ENV CHANGED ==
431 tests OK.
10 slowest tests:
- test_bigmem: 43 min 23 sec
- test_lzma: 34 min 18 sec
- test_bz2: 20 min 50 sec
- test_array: 7 min 23 sec
- test_zlib: 5 min 5 sec
- test_hashlib: 4 min 3 sec
- test_multiprocessing_spawn: 2 min 1 sec
- test_math: 1 min 32 sec
- test_pickle: 1 min 18 sec
- test_concurrent_futures: 1 min 14 sec
1 test altered the execution environment:
test_peg_generator
35 tests skipped:
test.test_asyncio.test_unix_events test_curses test_dbm_gnu
test_dbm_ndbm test_devpoll test_epoll test_fcntl test_fork1
test_gdb test_grp test_ioctl test_kqueue test_multiprocessing_fork
test_multiprocessing_forkserver test_nis test_openpty
test_ossaudiodev test_perf_profiler test_perfmaps test_pipes
test_poll test_posix test_pty test_pwd test_readline test_resource
test_spwd test_syslog test_threadsignals test_wait3 test_wait4
test_xxlimited test_xxtestfuzz test_zipfile64 test_zoneinfo
Total duration: 43 min 51 sec
Click to see traceback logs
remote: Enumerating objects: 13, done.
remote: Counting objects: 8% (1/12)
remote: Counting objects: 16% (2/12)
remote: Counting objects: 25% (3/12)
remote: Counting objects: 33% (4/12)
remote: Counting objects: 41% (5/12)
remote: Counting objects: 50% (6/12)
remote: Counting objects: 58% (7/12)
remote: Counting objects: 66% (8/12)
remote: Counting objects: 75% (9/12)
remote: Counting objects: 83% (10/12)
remote: Counting objects: 91% (11/12)
remote: Counting objects: 100% (12/12)
remote: Counting objects: 100% (12/12), done.
remote: Compressing objects: 11% (1/9)
remote: Compressing objects: 22% (2/9)
remote: Compressing objects: 33% (3/9)
remote: Compressing objects: 44% (4/9)
remote: Compressing objects: 55% (5/9)
remote: Compressing objects: 66% (6/9)
remote: Compressing objects: 77% (7/9)
remote: Compressing objects: 88% (8/9)
remote: Compressing objects: 100% (9/9)
remote: Compressing objects: 100% (9/9), done.
remote: Total 13 (delta 3), reused 8 (delta 3), pack-reused 1
From https://github.com/python/cpython
* branch 3.12 -> FETCH_HEAD
Note: switching to '637102980d12e5ff99b69ddffd5f05ecfe0adeb6'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:
git switch -c <new-branch-name>
Or undo this operation with:
git switch -
Turn off this advice by setting config variable advice.detachedHead to false
HEAD is now at 637102980d [3.12] gh-100238: Use setuptools in peg-generator and reenable tests (GH-104798) (#105135)
Switched to and reset branch '3.12'
Could Not Find R:\buildarea\3.12.ambv-bb-win11.bigmem\build\Lib\*.pyc
The system cannot find the file specified.
Could Not Find R:\buildarea\3.12.ambv-bb-win11.bigmem\build\PCbuild\python*.zip
Could Not Find R:\buildarea\3.12.ambv-bb-win11.bigmem\build\PCbuild\python*.zip
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Assignees
No one assigned
Milestone
No milestone
Development
Successfully merging this pull request may close these issues.
Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
|