Skip to content

Conversation

jkloth
Copy link
Contributor

@jkloth jkloth commented Dec 7, 2018

@jkloth jkloth requested a review from a team as a code owner December 7, 2018 01:08
<_RegistryVersion Condition="$(_RegistryVersion) != '' and !$(_RegistryVersion.EndsWith('.0'))">$(_RegistryVersion).0</_RegistryVersion>

<!-- The minimum allowed SDK version to use for building -->
<DefaultWindowsSDKVersion>10.0.10586.0</DefaultWindowsSDKVersion>
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I chose this SDK version as the minimum as I remember an issue ~5 years ago that was solved by using this version instead of an earlier one (although possibly pre-release).

@vstinner vstinner requested review from zware and zooba December 7, 2018 09:54
@vstinner
Copy link
Member

vstinner commented Dec 7, 2018

@zware, @zooba: Would you mind to have a look at this PR? @jkloth asked me to review it, but I don't know such VS specific feature.

@jkloth: You have to rebase/update your PR, there is a conflict: PCbuild/python.props

@vstinner
Copy link
Member

vstinner commented Dec 7, 2018

FYI it seems like PR #10245 introduced the conflict.

@vstinner
Copy link
Member

vstinner commented Dec 7, 2018

@zware, @zooba: Would you mind to have a look at this PR? @jkloth asked me to review it, but I don't know such VS specific feature.

Aha, @zooba approved the change in the bug tracker, but not here:
https://bugs.python.org/issue35433#msg331263

@zooba: I would prefer that you explicitly approve this change, since there are conflicts with your https://bugs.python.org/issue34977 change.


<!-- The minimum allowed SDK version to use for building -->
<DefaultWindowsSDKVersion>10.0.10586.0</DefaultWindowsSDKVersion>
<DefaultWindowsSDKVersion Condition="$(_RegistryVersion.CompareTo($(DefaultWindowsSDKVersion))) >= 0">$(_RegistryVersion)</DefaultWindowsSDKVersion>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just learned that a better way to spell this is:

$([System.Version]::Parse($(_RegistryVersion))) &gt; $([System.Version]::Parse($(DefaultWindowsSDKVersion)))

For the SDK version it probably won't matter though. The numbering scheme is going to remain the same length for a while.

@zooba zooba added the skip news label Dec 7, 2018
@zooba
Copy link
Member

zooba commented Dec 7, 2018

There are no conflicts. The only reason I didn't directly approve is because I was on my phone at the time and I can't post to GitHub properly from my phone (one of the reasons I voted against the move, and continue to vote against the move to put all issues on here).

In fixing my other PR, I found a better way to do the version comparison. So approved pending that change.

@vstinner
Copy link
Member

vstinner commented Dec 7, 2018

There are no conflicts.

Your two PRs modified the same file and the Merge button was disabled because of that. It's back to green because I reverted your App Store change.

@zooba
Copy link
Member

zooba commented Dec 7, 2018

Oh I see. In that case, this change will make mine unnecessary, but it's not directly related.

@miss-islington
Copy link
Contributor

Thanks @jkloth for the PR, and @zooba for merging it 🌮🎉.. I'm working now to backport this PR to: 3.6, 3.7.
🐍🍒⛏🤖

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Dec 10, 2018
@bedevere-bot
Copy link

GH-11058 is a backport of this pull request to the 3.7 branch.

@miss-islington
Copy link
Contributor

Sorry, @jkloth and @zooba, I could not cleanly backport this to 3.6 due to a conflict.
Please backport using cherry_picker on command line.
cherry_picker f46eccd0ffe65333035c3820886295b71c41ab6e 3.6

@bedevere-bot
Copy link

GH-11059 is a backport of this pull request to the 3.6 branch.

miss-islington added a commit that referenced this pull request Dec 10, 2018
(cherry picked from commit f46eccd)

Co-authored-by: Jeremy Kloth <[email protected]>
jkloth added a commit to jkloth/cpython that referenced this pull request Dec 10, 2018
@bedevere-bot
Copy link

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot AMD64 Windows8 3.6 has failed when building commit f04cc5f.

What do you need to do:

  1. Don't panic.
  2. Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
  3. Go to the page of the buildbot that failed (https://buildbot.python.org/all/#builders/38/builds/750) and take a look at the build logs.
  4. Check if the failure is related to this commit (f04cc5f) or if it is a false positive.
  5. 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/38/builds/750

Click to see traceback logs
From https://github.com/python/cpython
 * branch            3.6        -> FETCH_HEAD
Reset branch '3.6'

Could Not Find D:\buildarea\3.6.bolen-windows8\build\Lib\*.pyc
The system cannot find the file specified.
Could Not Find D:\buildarea\3.6.bolen-windows8\build\PCbuild\python*.zip

Could Not Find D:\buildarea\3.6.bolen-windows8\build\Lib\*.pyc
The system cannot find the file specified.
Could Not Find D:\buildarea\3.6.bolen-windows8\build\PCbuild\python*.zip

@bedevere-bot
Copy link

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot AMD64 Windows10 3.6 has failed when building commit f04cc5f.

What do you need to do:

  1. Don't panic.
  2. Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
  3. Go to the page of the buildbot that failed (https://buildbot.python.org/all/#builders/31/builds/718) and take a look at the build logs.
  4. Check if the failure is related to this commit (f04cc5f) or if it is a false positive.
  5. 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/31/builds/718

Click to see traceback logs
From https://github.com/python/cpython
 * branch            3.6        -> FETCH_HEAD
Reset branch '3.6'

Could Not Find D:\buildarea\3.6.bolen-windows10\build\Lib\*.pyc
The system cannot find the file specified.
Could Not Find D:\buildarea\3.6.bolen-windows10\build\PCbuild\python*.zip

Could Not Find D:\buildarea\3.6.bolen-windows10\build\Lib\*.pyc
The system cannot find the file specified.
Could Not Find D:\buildarea\3.6.bolen-windows10\build\PCbuild\python*.zip

@jkloth
Copy link
Contributor Author

jkloth commented Dec 10, 2018

Without knowing what version of VS2015 is used on Davd Bolen's buildbots for 3.6 these errors are nigh impossible to fix... These changes now force VS2015 to use the Win10 SDK whereas prior it was defaulting to the 8.1 SDK.

I have a message out to David regarding this.

@bedevere-bot
Copy link

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot AMD64 Windows8 3.6 has failed when building commit f04cc5f.

What do you need to do:

  1. Don't panic.
  2. Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
  3. Go to the page of the buildbot that failed (https://buildbot.python.org/all/#builders/38/builds/751) and take a look at the build logs.
  4. Check if the failure is related to this commit (f04cc5f) or if it is a false positive.
  5. 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/38/builds/751

Click to see traceback logs
Reset branch '3.6'

Could Not Find D:\buildarea\3.6.bolen-windows8\build\Lib\*.pyc
The system cannot find the file specified.
Could Not Find D:\buildarea\3.6.bolen-windows8\build\PCbuild\python*.zip

Could Not Find D:\buildarea\3.6.bolen-windows8\build\Lib\*.pyc
The system cannot find the file specified.
Could Not Find D:\buildarea\3.6.bolen-windows8\build\PCbuild\python*.zip

@bedevere-bot
Copy link

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot AMD64 Windows10 3.6 has failed when building commit f04cc5f.

What do you need to do:

  1. Don't panic.
  2. Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
  3. Go to the page of the buildbot that failed (https://buildbot.python.org/all/#builders/31/builds/719) and take a look at the build logs.
  4. Check if the failure is related to this commit (f04cc5f) or if it is a false positive.
  5. 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/31/builds/719

Click to see traceback logs
Reset branch '3.6'

Could Not Find D:\buildarea\3.6.bolen-windows10\build\Lib\*.pyc
The system cannot find the file specified.
Could Not Find D:\buildarea\3.6.bolen-windows10\build\PCbuild\python*.zip

Could Not Find D:\buildarea\3.6.bolen-windows10\build\Lib\*.pyc
The system cannot find the file specified.
Could Not Find D:\buildarea\3.6.bolen-windows10\build\PCbuild\python*.zip

@pablogsal
Copy link
Member

This commit broke the following (at least) the buildbots:

https://buildbot.python.org/all/#/builders/38/builds/751
https://buildbot.python.org/all/#/builders/31/builds/719

can someone work on a fix? Otherwise we would have to revert the commit per our policy with buildbot failures

@jkloth
Copy link
Contributor Author

jkloth commented Dec 11, 2018

There is a bit of a catch-22 here, if the changes get reverted, a different buildbot will be broken. Note that this is also actively being investigated,

@bedevere-bot
Copy link

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot AMD64 Windows10 3.6 has failed when building commit f04cc5f.

What do you need to do:

  1. Don't panic.
  2. Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
  3. Go to the page of the buildbot that failed (https://buildbot.python.org/all/#builders/31/builds/720) and take a look at the build logs.
  4. Check if the failure is related to this commit (f04cc5f) or if it is a false positive.
  5. 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/31/builds/720

Click to see traceback logs
Reset branch '3.6'

Could Not Find D:\buildarea\3.6.bolen-windows10\build\Lib\*.pyc
The system cannot find the file specified.
Could Not Find D:\buildarea\3.6.bolen-windows10\build\PCbuild\python*.zip

Could Not Find D:\buildarea\3.6.bolen-windows10\build\Lib\*.pyc
The system cannot find the file specified.
Could Not Find D:\buildarea\3.6.bolen-windows10\build\PCbuild\python*.zip

@jkloth jkloth deleted the issue35433 branch December 11, 2018 16:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants