-
Notifications
You must be signed in to change notification settings - Fork 41
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
Investigate regression cases found in integration tests after updating ScanCode #1183
Comments
I implemented a change to resolve the license issue for Nuget.Protocol coordinate. Now the code will only consider the matches if the score is greater than 80%. But it triggered other components to fail in the below mentioned places.
Scancode result -
Below is the licensed section from definition for changed code.
Here are the code changes related to this - yashkohli88#5 In my opinion regarding 'LicenseRef-scancode-unknown-license-reference' cases, this license match is triggered specifically by 'License' keyword present in those files. |
@yashkohli88 Thanks for the detailed explanation! I have summarized the findings of adding filtering below:
Cons:
|
As per our discussion, need to update the fixture and track the ones with regression in a documentation in operation repo. |
This comes from the discussion on PR to integrate new ScanCode, specifically on the license differences in integration tests before and after integrating v32 ScanCode.
The text was updated successfully, but these errors were encountered: