fix: remove outdated script, linter errors in build - #967
Merged
Conversation
lkomali
approved these changes
Oct 21, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Remove call to checkSMVER.sh script, which no longer exists. Triton used to call that script as a check in its entrypoint script until 22.03. That file has since been removed as an old artifact, so removing it here too.
For code hygiene, I also updated the copyrights, removed the echoing of the old copyright (no longer done in Triton), and updated the Dockerfile to use newer code semantics to get rid of linter warnings.
With these code updates, CI will now successfully build and run these Docker containers. I am working on fixing on the CI tests, but at least a few will run and pass on this branch (none pass on the main branch).