From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: gsl: update to 2.7.1, adopt.
Date: Sat, 11 Dec 2021 21:45:55 +0100 [thread overview]
Message-ID: <20211211204555.FkUnFDlpNmyQp7MLuvvGIvFnMBJ7kEv_Ub7CcHsPX1A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34469@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1970 bytes --]
New comment by tornaria on void-packages repository
https://github.com/void-linux/void-packages/pull/34469#issuecomment-991778989
Comment:
> ```
> aarch64-linux-gnu-g++: fatal error: cannot read spec file 'libgomp.spec': No such file or directory
> compilation terminated.
> ```
>
> Your cross builds might be hit by #31055
Hum... what shall I do?
The results of the CI are kind of weird; the one for x86_64 finished ok the first time and now it failed. Others failed because a download error (?). I worked hard to fix `do_check()` in four packages so this PR would work :thinking:
We discussed with @leahneukirchen on IRC how to setup CI so that it is possible to run xbps-src pkg without -Q on cases like this one:
```
10:31 < leah2> gt7: unfortunately not. i always wanted two actions, first build then
check, but it seems not possible to implement efficiently?
10:43 < gt7> leah2: maybe an option like [ci-skip] but [check-skip] which will still
run ./xbps-src pkg but without -Q ?
10:43 < leah2> yeah, could work
10:45 < gt7> I don't know anything about how github actions work, but the line
10:45 < gt7> TEST: '${{ matrix.config.test }}'
10:46 < gt7> if that can be made conditional to finding [check skip] on the PR title
or body, that may work
10:47 < gt7> it should be enough to have an expression that normally evaluates to
matrix.config.test, but yields 0 if [check skip] is present in the PR
10:48 -void-robot:#xbps- leahneukirchen pushed to void-packages (stress-ng: update to
0.13.08.)
10:49 < gt7> in fact looking at common/travis/build.sh, anything different than 1
works so maybe "[skip]" is better so that one can see at the matrix that
check was skipped by request
10:50 < gt7> I mean: set TEST to "[skip]" instead of 0 when "[check skip]" is
pressent in the PR
```
at least it would save time.
next prev parent reply other threads:[~2021-12-11 20:45 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 16:46 [PR PATCH] " tornaria
2021-12-11 2:44 ` ericonr
2021-12-11 20:45 ` tornaria [this message]
2021-12-13 19:16 ` leahneukirchen
2021-12-25 14:24 ` [PR PATCH] [Updated] " tornaria
2021-12-25 14:33 ` tornaria
2021-12-26 2:17 ` ericonr
2021-12-26 2:17 ` ericonr
2021-12-27 21:43 ` [PR PATCH] [Updated] " tornaria
2021-12-27 22:19 ` tornaria
2021-12-28 0:40 ` tornaria
2021-12-28 0:40 ` tornaria
2021-12-28 0:41 ` tornaria
2021-12-28 0:41 ` tornaria
2021-12-28 0:41 ` tornaria
2021-12-28 0:41 ` tornaria
2021-12-28 0:51 ` tornaria
2021-12-28 0:56 ` tornaria
2021-12-28 0:57 ` tornaria
2021-12-28 1:00 ` tornaria
2021-12-28 1:18 ` tornaria
2021-12-28 1:21 ` tornaria
2021-12-28 2:51 ` tornaria
2021-12-28 2:52 ` tornaria
2021-12-28 2:52 ` tornaria
2021-12-28 2:52 ` tornaria
2021-12-28 2:52 ` tornaria
2021-12-28 2:52 ` tornaria
2021-12-28 2:52 ` tornaria
2021-12-28 2:52 ` tornaria
2021-12-28 2:58 ` tornaria
2021-12-28 2:59 ` tornaria
2021-12-28 3:08 ` tornaria
2021-12-28 3:09 ` tornaria
2021-12-28 3:09 ` tornaria
2021-12-28 3:54 ` tornaria
2021-12-28 4:00 ` ericonr
2021-12-28 4:01 ` [PR PATCH] [Updated] " tornaria
2021-12-28 4:10 ` tornaria
2021-12-28 14:53 ` tornaria
2021-12-28 15:04 ` tornaria
2021-12-28 15:11 ` tornaria
2021-12-28 15:14 ` tornaria
2021-12-28 15:16 ` tornaria
2021-12-28 16:39 ` [PR PATCH] [Updated] " tornaria
2021-12-28 16:44 ` tornaria
2021-12-28 16:46 ` tornaria
2022-01-03 15:24 ` tornaria
2022-01-10 12:48 ` [PR PATCH] [Updated] " tornaria
2022-01-10 12:55 ` tornaria
2022-01-10 14:43 ` tornaria
2022-01-12 15:47 ` [PR PATCH] [Updated] " tornaria
2022-01-12 15:48 ` [PR PATCH] [Merged]: " leahneukirchen
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=20211211204555.FkUnFDlpNmyQp7MLuvvGIvFnMBJ7kEv_Ub7CcHsPX1A@z \
--to=tornaria@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).