-
Notifications
You must be signed in to change notification settings - Fork 139
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
fix: Unit Test Requires "test" Binary #266
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aahung
approved these changes
Aug 25, 2021
sriram-mv
approved these changes
Aug 25, 2021
sriram-mv
added a commit
that referenced
this pull request
Aug 31, 2021
* fix: improve support for pep517 builds (#265) * A pep517 build can declare build dependencies. Pip will then know to install these dependencies before trying to build a wheel file. * When creating a build environment, it's only guaranteed to last for the duration of the build process. It's not accessible once a pip command finishes running. * When we try to retrieve the version of a package we run a "modified" form of "python setup.py egg_info". * The problem with this is that we're not using the build environment that has all the build dependencies installed (it's already gone), so if setup.py imports a module (e.g. cython) because it expects it to be there because it declared it as a build dependency the egg_info command will fail. * We don't check the RC or have a fallback case if we can't generate egg info. * We fail with an indecipherable IndexError. We now have a fallback where if we can't import/run the setup.py file, we assume the PKG-INFO file should be in the top level directory of the sdist so we check if it's there, and if so we use that file. * Fixed Unit Test Requiring "test" Binary (#266) * fix(go version parts): remove alphabets from the version for validation (#259) * fix(go version parts): remove alphabets from the version for validation - Go versions like 1.12rc1 or 1.16beta1 are supported. - Test added. * fix: use regex for go versions * chore: aws lambda builders version set to 1.7.0 (#269) Co-authored-by: Cosh_ <[email protected]>
mndeveci
added a commit
that referenced
this pull request
Sep 29, 2021
* fix: improve support for pep517 builds (#265) * A pep517 build can declare build dependencies. Pip will then know to install these dependencies before trying to build a wheel file. * When creating a build environment, it's only guaranteed to last for the duration of the build process. It's not accessible once a pip command finishes running. * When we try to retrieve the version of a package we run a "modified" form of "python setup.py egg_info". * The problem with this is that we're not using the build environment that has all the build dependencies installed (it's already gone), so if setup.py imports a module (e.g. cython) because it expects it to be there because it declared it as a build dependency the egg_info command will fail. * We don't check the RC or have a fallback case if we can't generate egg info. * We fail with an indecipherable IndexError. We now have a fallback where if we can't import/run the setup.py file, we assume the PKG-INFO file should be in the top level directory of the sdist so we check if it's there, and if so we use that file. * Fixed Unit Test Requiring "test" Binary (#266) * fix(go version parts): remove alphabets from the version for validation (#259) * fix(go version parts): remove alphabets from the version for validation - Go versions like 1.12rc1 or 1.16beta1 are supported. - Test added. * fix: use regex for go versions * chore: aws lambda builders version set to 1.7.0 (#269) * test: Temporarily disabling two Python integration tests failing on Windows (#282) * feat: Allow Node.js projects to be built without requiring a package.json (#284) * Allow nodejs to build without requiring a manifest * Fix existing tests * Remove expected .package-lock * Define actions in the scope they're used * feat: ARM support (#25) (#287) Co-authored-by: Mathieu Grandis <[email protected]> * chore: bump version to 1.8.0 (#288) * fix: remove rendundant get_go_versions method (#290) Co-authored-by: Sriram Madapusi Vasudevan <[email protected]> Co-authored-by: Cosh_ <[email protected]> Co-authored-by: Mathieu Grandis <[email protected]> Co-authored-by: Daniel Mil <[email protected]>
CoshUS
added a commit
that referenced
this pull request
Sep 29, 2021
* fix: improve support for pep517 builds (#265) * A pep517 build can declare build dependencies. Pip will then know to install these dependencies before trying to build a wheel file. * When creating a build environment, it's only guaranteed to last for the duration of the build process. It's not accessible once a pip command finishes running. * When we try to retrieve the version of a package we run a "modified" form of "python setup.py egg_info". * The problem with this is that we're not using the build environment that has all the build dependencies installed (it's already gone), so if setup.py imports a module (e.g. cython) because it expects it to be there because it declared it as a build dependency the egg_info command will fail. * We don't check the RC or have a fallback case if we can't generate egg info. * We fail with an indecipherable IndexError. We now have a fallback where if we can't import/run the setup.py file, we assume the PKG-INFO file should be in the top level directory of the sdist so we check if it's there, and if so we use that file. * Fixed Unit Test Requiring "test" Binary (#266) * fix(go version parts): remove alphabets from the version for validation (#259) * fix(go version parts): remove alphabets from the version for validation - Go versions like 1.12rc1 or 1.16beta1 are supported. - Test added. * fix: use regex for go versions * chore: aws lambda builders version set to 1.7.0 (#269) * test: Temporarily disabling two Python integration tests failing on Windows (#282) * feat: Allow Node.js projects to be built without requiring a package.json (#284) * Allow nodejs to build without requiring a manifest * Fix existing tests * Remove expected .package-lock * Define actions in the scope they're used * feat: ARM support (#25) (#287) Co-authored-by: Mathieu Grandis <[email protected]> * chore: bump version to 1.8.0 (#288) * fix: remove rendundant get_go_versions method (#290) Co-authored-by: Sriram Madapusi Vasudevan <[email protected]> Co-authored-by: Cosh_ <[email protected]> Co-authored-by: Mathieu Grandis <[email protected]> Co-authored-by: Daniel Mil <[email protected]> Co-authored-by: Sriram Madapusi Vasudevan <[email protected]> Co-authored-by: Cosh_ <[email protected]> Co-authored-by: Mathieu Grandis <[email protected]> Co-authored-by: Daniel Mil <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue
The following tests do not mock path resolution which requires the system to have the binary "test".
Error:
This is fine for AppVeyor as "test" exists for Unix systems or Windows with Git installed in a certain way. However, on systems without "test" binary, unit tests will fail.
Description of changes:
Mocks all binary verification for workflow to better adhere to unit testing principles.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.