From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] [RFC] .github/workflows/build.yaml: add armv6l, armv7l-musl to build matrix
Date: Thu, 28 Jul 2022 18:34:09 +0200 [thread overview]
Message-ID: <20220728163409.KQALENUYBxJVtQTrYzqp_8X0M_JtkS8MGXPo1jiaaco@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38322@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 900 bytes --]
There is an updated pull request by classabbyamp against master on the void-packages repository
https://github.com/classabbyamp/void-packages ci/enable-all-archs
https://github.com/void-linux/void-packages/pull/38322
[RFC] .github/workflows/build.yaml: add armv6l, armv7l-musl to build matrix
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **NO** (but it's a trivial change)
This has been how it's done since at least the switch to github CI (#26095), and how it was done in the travis CI era:
https://github.com/void-linux/void-packages/blob/71a25f3e735c1fef4178422b1a2bb70ec8e84e02/.travis.yml#L15-L21
Should it be changed? Is there a reason why CI isn't currently run on armv6l and armv7l-musl?
A patch file from https://github.com/void-linux/void-packages/pull/38322.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-ci/enable-all-archs-38322.patch --]
[-- Type: text/x-diff, Size: 1159 bytes --]
From cd3040f7617fe19ed9effbb7a1062c9ffd8eddf0 Mon Sep 17 00:00:00 2001
From: classabbyamp <void@placeviolette.net>
Date: Wed, 27 Jul 2022 19:16:22 -0400
Subject: [PATCH] .github/workflows/build.yaml: add armv6l, armv7l-musl to
build matrix
---
.github/workflows/build.yaml | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/.github/workflows/build.yaml b/.github/workflows/build.yaml
index bb05364b5e74..8931e6cf53f5 100644
--- a/.github/workflows/build.yaml
+++ b/.github/workflows/build.yaml
@@ -58,9 +58,11 @@ jobs:
- { arch: i686, bootstrap: i686, test: 1 }
- { arch: aarch64, bootstrap: x86_64, test: 0 }
- { arch: armv7l, bootstrap: x86_64, test: 0 }
+ - { arch: armv6l, bootstrap: x86_64, test: 0 }
- { arch: x86_64-musl, bootstrap: x86_64-musl, test: 1 }
- - { arch: armv6l-musl, bootstrap: x86_64-musl, test: 0 }
- { arch: aarch64-musl, bootstrap: x86_64-musl, test: 0 }
+ - { arch: armv7l-musl, bootstrap: x86_64-musl, test: 0 }
+ - { arch: armv6l-musl, bootstrap: x86_64-musl, test: 0 }
steps:
- name: Prepare container
next prev parent reply other threads:[~2022-07-28 16:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 23:22 [PR PATCH] " classabbyamp
2022-07-28 16:34 ` classabbyamp [this message]
2022-07-30 13:35 ` Chocimier
2022-07-31 7:25 ` classabbyamp
2022-07-31 7:25 ` [PR PATCH] [Closed]: " classabbyamp
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=20220728163409.KQALENUYBxJVtQTrYzqp_8X0M_JtkS8MGXPo1jiaaco@z \
--to=classabbyamp@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).