Github messages for voidlinux
 help / color / mirror / Atom feed
From: st3r4g <st3r4g@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: intel-compute-runtime-20.18.16699
Date: Wed, 13 May 2020 00:22:04 +0200	[thread overview]
Message-ID: <20200512222204.g1QaaVfJ30-kp6ELXS6wzMrYl0ApUGbBEIL6SHNjE9c@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21855@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 398 bytes --]

New comment by st3r4g on void-packages repository

https://github.com/void-linux/void-packages/pull/21855#issuecomment-627630163

Comment:
Some tests are failing:
```
[ 93%] Built target run_kbl_unit_tests
running tests for linux dynamic library - .so in /builddir/compute-runtime-20.18.16699/build/bin
```
In this stage a lot of checks fail and there is even a segfault. Other stages seem ok

  parent reply	other threads:[~2020-05-12 22:22 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-11 23:48 [PR PATCH] " st3r4g
2020-05-12  6:21 ` [PR PATCH] [Updated] " st3r4g
2020-05-12  7:18 ` st3r4g
2020-05-12  7:26 ` st3r4g
2020-05-12  8:13 ` ericonr
2020-05-12 18:02 ` ericonr
2020-05-12 19:17 ` st3r4g
2020-05-12 20:15 ` [PR PATCH] [Updated] " st3r4g
2020-05-12 21:36 ` st3r4g
2020-05-12 22:22 ` st3r4g [this message]
2020-05-12 22:38 ` st3r4g
2020-05-13  9:54 ` [PR PATCH] [Updated] " st3r4g
2020-05-13 10:04 ` st3r4g
2020-05-13 12:25 ` st3r4g
2020-05-14 19:11 ` [PR PATCH] [Updated] " st3r4g
2020-05-14 21:09 ` st3r4g
2020-05-16 14:19 ` st3r4g
2020-05-16 14:23 ` st3r4g
2020-05-18  1:58 ` ericonr
2020-05-18  2:04 ` ericonr
2020-05-18  2:08 ` ericonr
2020-05-18  2:27 ` ericonr
2020-05-18  2:40 ` ericonr
2020-05-18  2:42 ` ericonr
2020-05-18  2:42 ` ericonr
2020-05-18  8:27 ` st3r4g
2020-05-18 21:55 ` [PR PATCH] [Updated] " st3r4g
2020-05-22 20:09 ` ericonr
2020-05-22 21:05 ` [PR PATCH] [Updated] " st3r4g
2020-05-22 21:07 ` st3r4g
2020-05-22 21:08 ` ericonr
2020-05-22 21:18 ` st3r4g
2020-05-22 21:21 ` [PR PATCH] [Updated] " st3r4g
2020-05-29 17:55 ` New package: intel-compute-runtime-20.20.16837 ericonr
2020-05-29 18:03 ` ericonr
2020-05-29 18:07 ` ericonr
2020-05-29 20:22 ` ericonr
2020-05-29 20:23 ` ericonr
2020-05-29 20:27 ` [PR PATCH] [Updated] " st3r4g
2020-11-22  5:17 ` New package: intel-compute-runtime-20.21.16886 the-maldridge
2020-11-22 15:02 ` ericonr
2020-11-22 15:02 ` ericonr
2020-11-22 17:45 ` st3r4g
2021-05-19  3:51 ` ericonr
2022-04-16  2:02 ` github-actions
2022-05-01  2:13 ` [PR PATCH] [Closed]: " github-actions

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200512222204.g1QaaVfJ30-kp6ELXS6wzMrYl0ApUGbBEIL6SHNjE9c@z \
    --to=st3r4g@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).