public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Agostino Sarubbo <ago@gentoo.org>
To: John Helmert III <ajak@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Disturbing state of arch testing in Gentoo
Date: Sun, 06 Nov 2022 20:03:16 +0100	[thread overview]
Message-ID: <1756803.VLH7GnMWUR@spectre> (raw)
In-Reply-To: <Y2e2TJ0i/4z+c/3b@gentoo.org>

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

On domenica 6 novembre 2022 14:27:40 CET John Helmert III wrote:
> As far as I can tell, there's ONE person relying completely on a
> proprietary arch testing system.
> 
> Ago, could you comment on this? What's blocking you from open sourcing
> your software?

Hi,

I already answered in the previous post:

"I still use getatoms.py to fetch 'doable' stablereqs (it is on my todo 
to switch to nattka). And I have a script the **simply** does emerge over the list of 
the packages. There is nothing obscure in it."

I'm working in arch testing since 2009. In the past I relied on scripts done by someone else 
and every time there was an issue I got no response.
At a certain point I decided to make my own script in language I know so I can edit it when 
is needed.


Since few years we allow self stabilization from maintainer. Do we know how and with 
what they test? No because it is not required.
The requirement for test is that the package you are testing works as expected.

https://wiki.gentoo.org/wiki/Project:AMD64_Arch_Testers#Arch_tester.27s_policy[1]

Agostino

--------
[1] https://wiki.gentoo.org/wiki/Project:AMD64_Arch_Testers#Arch_tester.27s_policy

[-- Attachment #2: Type: text/html, Size: 2762 bytes --]

  reply	other threads:[~2022-11-06 19:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-06  8:15 [gentoo-dev] Disturbing state of arch testing in Gentoo Michał Górny
2022-11-06  8:34 ` Sam James
2022-11-08  4:58   ` Arthur Zamarin
2022-11-06 10:37 ` Piotr Karbowski
2022-11-07  6:07   ` Oskari Pirhonen
2022-11-07  6:26     ` Joonas Niilola
2022-11-07 15:13       ` John Helmert III
2022-11-08  7:40       ` Oskari Pirhonen
2022-11-07 23:16     ` Sam James
2022-11-08  0:23       ` Rich Freeman
2022-11-08  0:30         ` Sam James
2022-11-08  0:34         ` John Helmert III
2022-11-08  0:54           ` Rich Freeman
2022-11-08  6:06         ` Joonas Niilola
2022-11-08 13:26         ` Michał Górny
2022-11-08 13:55           ` Agostino Sarubbo
2022-11-06 13:27 ` John Helmert III
2022-11-06 19:03   ` Agostino Sarubbo [this message]
2022-11-06 19:15     ` John Helmert III
2022-11-06 18:50 ` Agostino Sarubbo
2022-11-08  8:43 ` Agostino Sarubbo
2022-11-08 15:18   ` John Helmert III

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=1756803.VLH7GnMWUR@spectre \
    --to=ago@gentoo.org \
    --cc=ajak@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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