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
APT whitelist request for fglrx #383
Comments
Ran tests and found setuid bits by purely textual search. Further analysis is required. If these are found to be benign, add: fglrx fglrx-dev fglrx-amdcccle See https://travis-ci.org/travis-ci/apt-whitelist-checker/builds/72545436. |
Any news on this one? Can I help move it forward? |
Likewise, is there anything I can do to get help move this forward? |
👍 waiting for an update on this |
As the offending bits were found in binary files, I don't know if we can enable this. Sorry. |
Thanks for your answer. In that case, what other options do we have to test OpenCL code using the container infrastructure? |
There isn't. The recent "Docker" infrastructure is on a different infrastructure, and you can use |
@ntessore I've had some success with testing OpenCL code using the OSX build machines. I'm not sure if I'm breaking any rules here though. I'm using the legacy infrastructure (set |
|
Packages: fglrx fglrx-dev fglrx-amdcccle
This is an automated comment. Ran tests and found setuid bits by purely textual search. Further analysis is required. If these are found to be benign, examine http://github.com/travis-ci/apt-package-whitelist/compare/test-apt-package-whitelist-383 and its PR. Packages found: fglrx fglrx-dev fglrx-amdcccle See https://travis-ci.org/travis-ci/apt-whitelist-checker/builds/440489958 for details. |
This replaces travis-ci/travis-ci#4228.
The original text by @safl follows
The text was updated successfully, but these errors were encountered: