| Summary: | download-github-release.py hits errors on Windows bots | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Alexey Proskuryakov <ap> | ||||
| Component: | Tools / Tests | Assignee: | Fujii Hironori <Hironori.Fujii> | ||||
| Status: | RESOLVED FIXED | ||||||
| Severity: | Normal | CC: | bfulgham, dbates, don.olmstead, ews-watchlist, Hironori.Fujii, lforschler, pvollan, ross.kirsling, stephan.szabo | ||||
| Priority: | P2 | ||||||
| Version: | Other | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Attachments: |
|
||||||
|
Description
Alexey Proskuryakov
2018-09-07 10:12:47 PDT
Is there a network issue on the AppleWin bots? Nothing about how update-vswhere is called has changed since it was introduced in bug 175275, but it's tricky to know when this started occurring, as all of the existing logs contain this error. Could be intentionally limited network ACL. May have well been happening from the start, I just didn’t look before. Is this script doing something that Apple Windows port needs? With the move to using VS 2017, it no longer really has a singular install location to use, nor can you rely on getting the version directly from the install location. vswhere finds the install location and version, the update script is just checking for the newest version of vswhere to upgrade to. That might not be important for applewin depending on whether apple's IT policy prevents anything other than the default community location. For wincairo builds we’re using the build tools version https://visualstudio.microsoft.com/downloads/ which is meant for build servers. There’s no IDE included. It installs in a different location than community. Created attachment 353273 [details]
Patch
Comment on attachment 353273 [details]
Patch
Informal r-
The vswhere call is there for a reason. Its to verify that there is a visual studio version that can build webkit. If the thing is failing it should have more error checking and a potential fallback path.
Using vswhere causes the compiler version mismatch problem (Bug 190797 Comment 24). CMake looks for VS by its own logic. We should use vcvars64.bat to safely choose a VS installation. If you have multiple VS installations, there are mulptile "x64 Native Tools Command Prompt for Visual Studio 2017" menu items in Windows Start menu. You can use which you want to choose VS. It seems that AppleWin BuildBot issue has been fixed. I will file another bug for the mismatch issue. |