Skip to content
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

OpenCL driver null when running GPU test (Trac #1267) #1843

Closed
wpotrzebowski opened this issue Mar 30, 2019 · 8 comments
Closed

OpenCL driver null when running GPU test (Trac #1267) #1843

wpotrzebowski opened this issue Mar 30, 2019 · 8 comments
Assignees
Milestone

Comments

@wpotrzebowski
Copy link
Contributor

When running GPU test OpenCL driver (clinfo) returns null. It seems like it is related to recent change in sasmodels.kernelcl.enviroment() change

Migrated from http://trac.sasview.org/ticket/1267

{
    "status": "assigned",
    "changetime": "2019-03-29T16:19:20",
    "_ts": "2019-03-29 16:19:20.840688+00:00",
    "description": "When running GPU test OpenCL driver (clinfo) returns null. It seems like it is related to recent change in sasmodels.kernelcl.enviroment() change",
    "reporter": "wojciech",
    "cc": "",
    "resolution": "",
    "workpackage": "SasView Bug Fixing",
    "time": "2019-03-29T16:07:54",
    "component": "sasmodels",
    "summary": "OpenCL driver null when running GPU test",
    "priority": "major",
    "keywords": "",
    "milestone": "sasmodels 1.0",
    "owner": "wojciech",
    "type": "defect"
}
@wpotrzebowski wpotrzebowski self-assigned this Mar 30, 2019
@wpotrzebowski
Copy link
Contributor Author

Trac update at 2019/03/29 16:19:20:

  • wojciech changed owner from "" to "wojciech"
  • wojciech changed status from "new" to "assigned"

@pkienzle
Copy link
Contributor

See #219. This should now be fixed.

@butlerpd
Copy link
Member

why was this changed to sasview 4.3? there should not be any sasview 4.3 tickets in sasmodels. Should this be moved to the sasview repo?

@butlerpd butlerpd transferred this issue from SasView/sasmodels Mar 16, 2020
@butlerpd
Copy link
Member

@wpotrzebowski, is this now fixed? if so we can close this ticket

@butlerpd
Copy link
Member

butlerpd commented May 2, 2021

@wpotrzebowski is this fixed by #219 as suggested? if so we need to close this ticket. If not we should move it to the next milestone since 5.0.4 is now done.

@wpotrzebowski
Copy link
Contributor Author

@butlerpd: yes it should be fixed now and can be closed.

@butlerpd
Copy link
Member

butlerpd commented May 8, 2021

The fix is a PR in sasmodels so apparently this issue should indeed reside in sasmodels. I will move it back then close

@butlerpd butlerpd transferred this issue from SasView/sasview May 8, 2021
@butlerpd butlerpd transferred this issue from SasView/sasmodels May 8, 2021
@butlerpd butlerpd added this to the SasView 4.2.2 milestone May 8, 2021
@butlerpd
Copy link
Member

butlerpd commented May 8, 2021

Clearly making a meal of this one. #219 is in fact a sasview PR (that references issues in both). Since the PR was merged on April 2 of 2019 into branch master it was part of release 4.2.2. I have thus changed the milestone accordingly and now closing this ticket.

@butlerpd butlerpd closed this as completed May 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants