Skip to content

Update REUSE to v3.3. Add REUSE-Ignore wrapper to remove warnings #746

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.

Sign up for GitHub

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

Jump to bottom
Open
KhronosWebservices wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update REUSE to v3.3. Add REUSE-Ignore wrapper to remove warnings #746

KhronosWebservices wants to merge 1 commit into from
+74 −52

Conversation

@KhronosWebservices
Copy link
Member

@KhronosWebservices KhronosWebservices commented Jan 16, 2026

No description provided.

@KhronosWebservices KhronosWebservices requested a review from a team as a code owner January 16, 2026 20:08
@KhronosWebservices KhronosWebservices changed the title Update REUSE to v6.1. Add REUSE-Ignore wrapper to remove warnings Update REUSE to v3.3. Add REUSE-Ignore wrapper to remove warnings Jan 16, 2026
@CLAassistant
Copy link

CLAassistant commented Jan 16, 2026 •
edited
Loading

CLA assistant check
All committers have signed the CLA.

@KhronosWebservices
Copy link
Member Author

KhronosWebservices commented Jan 23, 2026

The error being thrown is unfamiliar. Any suggestions? Is adding # REUSE-IgnoreStart and # REUSE-IgnoreEnd comments enough to break this?

@swoods-nv
Copy link
Contributor

swoods-nv commented Jan 27, 2026

Sorry for missing this review notification! Is the question about the error being thrown referring to the ci failure? If so-- that looks like an access violation triggered in some GPU code in one of the unit tests, shouldn't have anything to do with this PR. I've rerun the job just to be sure.

@allcreatures
Copy link
Contributor

allcreatures commented Jan 27, 2026

Sorry for missing this review notification! Is the question about the error being thrown referring to the ci failure? If so-- that looks like an access violation triggered in some GPU code in one of the unit tests, shouldn't have anything to do with this PR. I've rerun the job just to be sure.
No worries. Yes, that was my concern.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@swoods-nv swoods-nv Awaiting requested review from swoods-nv

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@KhronosWebservices @CLAassistant @swoods-nv @allcreatures