-
Notifications
You must be signed in to change notification settings - Fork 474
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
🌱 Update binary_analysis and license tests #4078
Closed
Closed
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
seelder
requested review from
naveensrinivasan and
raghavkaul
and removed request for
a team
May 3, 2024 18:08
seelder
changed the title
🌱 Update binary_analysis and license tests (#4032)
🌱 Update binary_analysis and license tests
May 3, 2024
Signed-off-by: seelder <seelder@ncsu.edu>
Updated the test to use scut. Updated the test data to use scut, including adding NumberOfInfo and NumberOfWarn for each test case Signed-off-by: seelder <seelder@ncsu.edu>
First attempt at updating license_test to use gomock instead of localDir. Note: localDir currently has a TODO for implementing ListLicenses. It returns an UnsupportedFeatures error, which is then handled in checks/raw/license. This first attempt replicates that existing behavior. Signed-off-by: seelder <seelder@ncsu.edu>
Clarified why the mock simply throws an error Signed-off-by: seelder <seelder@ncsu.edu>
Bumps [github.com/moby/buildkit](https://github.com/moby/buildkit) from 0.13.1 to 0.13.2. - [Release notes](https://github.com/moby/buildkit/releases) - [Commits](moby/buildkit@v0.13.1...v0.13.2) --- updated-dependencies: - dependency-name: github.com/moby/buildkit dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Signed-off-by: seelder <seelder@ncsu.edu>
* switch signed-releases lookback limit precedence if the 6th release had no assets, the lookback limit exit condition was being skipped. This led to scenarios where too many releases were being considered by the Signed-Releases check. ossf#4059 Signed-off-by: Spencer Schrock <sschrock@google.com> * make exit condition stronger any release after the lookback should be skipped Signed-off-by: Spencer Schrock <sschrock@google.com> --------- Signed-off-by: Spencer Schrock <sschrock@google.com> Signed-off-by: seelder <seelder@ncsu.edu>
Signed-off-by: afmarcum <138055109+afmarcum@users.noreply.github.com> Signed-off-by: seelder <seelder@ncsu.edu>
I keep trying to fix the errors but it seems to be making it worse. If I need to start over, let me know. |
Signed-off-by: seelder <seelder@ncsu.edu>
Updated the test to use scut. Updated the test data to use scut, including adding NumberOfInfo and NumberOfWarn for each test case Signed-off-by: seelder <seelder@ncsu.edu>
First attempt at updating license_test to use gomock instead of localDir. Note: localDir currently has a TODO for implementing ListLicenses. It returns an UnsupportedFeatures error, which is then handled in checks/raw/license. This first attempt replicates that existing behavior. Signed-off-by: seelder <seelder@ncsu.edu>
Clarified why the mock simply throws an error Signed-off-by: seelder <seelder@ncsu.edu>
Bumps [github.com/moby/buildkit](https://github.com/moby/buildkit) from 0.13.1 to 0.13.2. - [Release notes](https://github.com/moby/buildkit/releases) - [Commits](moby/buildkit@v0.13.1...v0.13.2) --- updated-dependencies: - dependency-name: github.com/moby/buildkit dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Signed-off-by: seelder <seelder@ncsu.edu>
* switch signed-releases lookback limit precedence if the 6th release had no assets, the lookback limit exit condition was being skipped. This led to scenarios where too many releases were being considered by the Signed-Releases check. ossf#4059 Signed-off-by: Spencer Schrock <sschrock@google.com> * make exit condition stronger any release after the lookback should be skipped Signed-off-by: Spencer Schrock <sschrock@google.com> --------- Signed-off-by: Spencer Schrock <sschrock@google.com> Signed-off-by: seelder <seelder@ncsu.edu>
Signed-off-by: afmarcum <138055109+afmarcum@users.noreply.github.com> Signed-off-by: seelder <seelder@ncsu.edu>
Signed-off-by: seelder <seelder@ncsu.edu>
Signed-off-by: seelder <seelder@ncsu.edu>
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.
What kind of change does this PR introduce?
Updates tests to follow best practices
(Is it a bug fix, feature, docs update, something else?)
What is the current behavior?
binary_analysis and license check tests currently use localDirRepo instead of gomock
binary_analysis does not utilize scut (license test already uses scut and does not need modification)
What is the new behavior (if this is a feature change)?**
Which issue(s) this PR fixes
Addresses #4032