Github messages for voidlinux
 help / color / mirror / Atom feed
From: bobertlo <bobertlo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: [RFC] build-styles/go.sh: run go test -v ${go_project:-go_import_path} in do_check
Date: Sat, 29 Jan 2022 01:12:22 +0100	[thread overview]
Message-ID: <20220129001222.Pw2AoxrOvoJFOAL90MSjYFSgY9i5cIG7PQ4iu_jvv58@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34496@inbox.vuxu.org>

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

There's a closed pull request on the void-packages repository

[RFC] build-styles/go.sh: run go test -v ${go_project:-go_import_path} in do_check
https://github.com/void-linux/void-packages/pull/34496

Description:
There are 313 build_style=go packages, and currently 8 of them have tests defined in the package template.

I have been testing the go packages with this. So far, I have rebuilt 183 packages and there have been no errors and 64 packages have run tests successfully.

Ideally, more tests would be added (because they are a lot more common on internal libraries than command clients) but this is probably the safest default option.

EDIT: My script was setup wrong and some packages did fail. I am testing with only running tests on packages that have a `go.mod` and the pass rate is very high. I will see how this goes.

      parent reply	other threads:[~2022-01-29  0:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-12 20:19 [PR PATCH] " bobertlo
2021-12-13  3:00 ` [PR PATCH] [Updated] " bobertlo
2022-01-29  0:12 ` bobertlo
2022-01-29  0:12 ` bobertlo [this message]

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=20220129001222.Pw2AoxrOvoJFOAL90MSjYFSgY9i5cIG7PQ4iu_jvv58@z \
    --to=bobertlo@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).