-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add 'make generate' script for Windows #1893
Conversation
14d38dc
to
fca43d9
Compare
This should be either a python or cmake script so it uses the same script for both windows and linux. |
Codecov Report
@@ Coverage Diff @@
## develop #1893 +/- ##
========================================
Coverage 91.37% 91.37%
========================================
Files 419 419
Lines 15544 15544
========================================
Hits 14204 14204
Misses 1340 1340 |
This build is not recommended to merge 🔴 |
🔴cadene-dpn92_1: FAILED: MIGraphX is not within tolerance - check verbose output |
fca43d9
to
82f6680
Compare
:: | ||
:: The MIT License (MIT) | ||
:: | ||
:: Copyright (c) 2015-2022 Advanced Micro Devices, Inc. All rights reserved. |
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.
2023
I agree, a unified script for Linux and Windows is preferred. Our mandate for these initial changes was to minimally impact Linux. Are you okay if we generate a work item to address this after all the Windows changes have made it upstream? The reasoning is that this change is blocking Windows and the work for a new unified script has a testing requirement for both Windows and Linux that will take some time and is lower priority compared to enabling the larger Windows effort. |
|
Fair point. It is still additional work that affects Linux more directly. Our goal for the initial changes was to minimally impact Linux and follow your patterns. The pattern here was to solve this problem with a shell script and we solved it with a shell script for Windows. We can change the pattern and create a unified script that works on both OS but it could potentially affect Linux which increases the testing work. I think we should consider a change in goal. A modest increase in Linux risk is okay if we create a unified solution. We'll pull the change, move it to another branch, and hold onto the branch until we have time to do the unified solution. |
The PR from the series to enable MIGraphX on Windows.