GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||||||||||||
GeezerVison is showing github.com — gh-87868: Skip some test in `test_subprocess` if python is configured with --enable-shared by aisk · Pull Request #113867 · python/cpython Conversation
|
|
Can you update the PR title to more accurately reflect the change? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
🤖 New build scheduled with the buildbot fleet by @erlend-aasland for commit 4f22675 🤖 If you want to schedule another build, you need to add the 🔨 test-with-buildbots label again. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
How about this? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
I was thinking that perhaps we could determine the PR title later, if we addressed the issue, and fixed it in this PR. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Instead of describing the git diff, I would try to write the PR title so it reflects the change in behaviour. For example, a PR can fix a flakey test by making the test environment deterministic. If you are scrolling through the git log it is more helpful to read about what effect a commit had. We can always check the diff by doing |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
I wouldn't expect this to fix it, btw. It's just going to improve the output when it fails. So we can review the buildbot results with this change and figure out the actual fix, and then do that as part of this PR (which will then need a different title) |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Really thanks! I've learnt a lot from this. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Co-authored-by: Steve Dower <[email protected]>
test_subprocess
|
The failed test environment is Linux based, like https://buildbot.python.org/all/#/builders/543/builds/5159 . |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
You are right; I assumed it was Windows-specific, since the previous PR was Windows oriented. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Co-authored-by: Steve Dower <[email protected]>
test_subprocesstest_subprocess if python is configured with --enable-shared
|
Sorry, |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
!buildbot .64 (RHEL|Fedora Stable). |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
🤖 New build scheduled with the buildbot fleet by @erlend-aasland for commit 5671246 🤖 The command will test the builders whose names match following regular expression: The builders matched are:
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
We should also be able to run the test by copying |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
The main intent of this test is to determine if we correctly handle the off-by-one problems in the for loops within the sort and de-duplication functions. For example, do we missed something if there is just one element in the environment keys. Therefore I think we can't copy the |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Sorry, @aisk and @gpshead, I could not cleanly backport this to |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Sorry, @aisk and @gpshead, I could not cleanly backport this to |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
oh, backports do not appear to be needed. yay. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
thanks for the fix! this test is indeed somewhat fragile and only easy to run on some platforms - skipping it when it cannot be run is fine. we've still got coverage elsewhere. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
…ess` when the platform or build cannot do that (python#113867) * improve the assert for test_one_environment_variable * skip some test in test_subprocess when python is configured with shared * also skip the test if AddressSanitizer is enabled --------- Co-authored-by: Steve Dower <[email protected]>
…ess` when the platform or build cannot do that (python#113867) * improve the assert for test_one_environment_variable * skip some test in test_subprocess when python is configured with shared * also skip the test if AddressSanitizer is enabled --------- Co-authored-by: Steve Dower <[email protected]>
…ess` when the platform or build cannot do that (python#113867) * improve the assert for test_one_environment_variable * skip some test in test_subprocess when python is configured with shared * also skip the test if AddressSanitizer is enabled --------- Co-authored-by: Steve Dower <[email protected]>
…ess` when the platform or build cannot do that (python#113867) * improve the assert for test_one_environment_variable * skip some test in test_subprocess when python is configured with shared * also skip the test if AddressSanitizer is enabled --------- Co-authored-by: Steve Dower <[email protected]>
…ess` when the platform or build cannot do that (python#113867) * improve the assert for test_one_environment_variable * skip some test in test_subprocess when python is configured with shared * also skip the test if AddressSanitizer is enabled --------- Co-authored-by: Steve Dower <[email protected]>
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.