Dai-Ni Hsieh
Dai-Ni Hsieh
Definitely. This was closed automatically by github. I guess github grabbed it from the description in #167. I will open a new issue for the problem of cuBLAS, but I...
Reopen this issue as we still not cover cuBLAS and cuSOLVER.
@npmiller Would it be possible for you to take a look at this issue when you have a chance? Based on your experience of PR #136, Mesut (@mmeterel) suggests that...
@npmiller Thank you so much for the investigation! @andrewtbarker Could you take a look please?
Close this issue as it cannot be reproduced now. It appears to be related to machine environment and/or compiler packages.
Although usually I don't like to start something and not complete it, I need to give up this time due to my recent schedule. Please take it from here. Thanks!
I can do it this weekend, but feel free to open a PR if someone is available sooner.
An indirectly related question: I noticed that previous workflows were run on [my forked repo](https://github.com/dnhsieh-intel/oneMKL/actions). Do you think a condition like [this](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#example-only-run-job-for-specific-repository) can avoid the runs on forked repos?
I see. I hope GitHub can provide a more maintainable way for this. At the same time, we may need to communicate this with contributors, but this is out of...
I would suggest NOT changing the landing README file. The changes would make the table hard to interpret and inconsistent.