ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: Paul Wolneykien <manowar@altlinux.org>
To: devel@lists.altlinux.org
Subject: Re: [devel] Q: Do not EPERM test-only tasks
Date: Thu, 3 Dec 2020 23:24:51 +0300
Message-ID: <20201203232451.474b46a7@rigel.localdomain> (raw)
In-Reply-To: <9244c0cc-d4ed-f264-7d33-6cca005f1065@basealt.ru>

В Thu, 3 Dec 2020 21:50:30 +0300
Anton Farygin <rider@basealt.ru> пишет:

> On 03.12.2020 21:44, Vitaly Chikunov wrote:
> > On Thu, Dec 03, 2020 at 09:36:16PM +0300, Anton Farygin wrote:  
> >> On 03.12.2020 21:30, Vitaly Chikunov wrote:  
> >>> On Thu, Dec 03, 2020 at 09:26:34PM +0300, Dmitry V. Levin wrote:  
> >>>> On Thu, Dec 03, 2020 at 09:14:02PM +0300, Vitaly Chikunov wrote:
> >>>>  
> >>>>> Hi,
> >>>>>
> >>>>> Предлагаю test-only таски не переводить в состояние EPERM. Это
> >>>>> позволит легко отличить в почте результат run --test-only от
> >>>>> run --commit!  
> >>>> А в какое состояние тогда их переводить?  
> >>> Варианты: TESTED, TESTEPERM,  
> >> не надо использовать термин TESTED для заданий, которые не TESTED.
> >>  
> > Я думаю, что не надо смешивать разные feature requests в один.  
> 
> Да, ок. Давай этого медведя есть маленькими кусочками.
> 
> не показывать EPERM для заданий, у которых не может быть EPERM потому 
> что они тестовые - эта идея отличная и, наверное, станет легче.

  +1


  reply	other threads:[~2020-12-03 20:24 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-03 18:14 Vitaly Chikunov
2020-12-03 18:18 ` Aleksey Novodvorsky
2020-12-03 18:26 ` Dmitry V. Levin
2020-12-03 18:30   ` Vitaly Chikunov
2020-12-03 18:36     ` Anton Farygin
2020-12-03 18:44       ` Vitaly Chikunov
2020-12-03 18:50         ` Anton Farygin
2020-12-03 20:24           ` Paul Wolneykien [this message]
2020-12-04  8:28           ` Sergey V Turchin
2020-12-05 16:29           ` [devel] Q: ON_QA Dmitry V. Levin
2020-12-05 17:18             ` Vitaly Chikunov
2020-12-05 18:46               ` Anton Farygin
2020-12-07 10:55             ` Новиков Сергей
2020-12-07 11:01               ` Michael Shigorin
2020-12-07 11:12                 ` Anton Farygin
2020-12-07 11:16                 ` Paul Wolneykien
2020-12-07 11:16                 ` Sergey V Turchin
2020-12-07 11:15               ` Arseny Maslennikov
2020-12-07 11:19                 ` Anton Farygin
2020-12-07 11:29                 ` Michael Shigorin
2020-12-08 17:10               ` Dmitry V. Levin
2020-12-09  8:50                 ` Новиков Сергей
2020-12-09 10:24                   ` Alexey V. Vissarionov
2020-12-03 18:51     ` [devel] Q: Do not EPERM test-only tasks Dmitry V. Levin
2020-12-03 18:56       ` Anton Farygin
2020-12-03 19:00         ` Dmitry V. Levin
2020-12-03 19:07           ` Anton Farygin
2020-12-03 19:18             ` Dmitry V. Levin
2020-12-03 19:22               ` Anton Farygin
2020-12-04  8:30           ` Sergey V Turchin
2020-12-03 19:04       ` Vitaly Chikunov
2020-12-03 19:16         ` Dmitry V. Levin
2020-12-03 19:27           ` Dmitry V. Levin
2020-12-03 19:54             ` Denis Medvedev
2020-12-03 19:58               ` Michael Shigorin
2020-12-03 19:59               ` Dmitry V. Levin
2020-12-03 20:10                 ` Denis Medvedev
2020-12-03 20:11                   ` Michael Shigorin
2020-12-03 20:03             ` Vitaly Chikunov
2020-12-03 20:10               ` Dmitry V. Levin
2020-12-03 20:49               ` Paul Wolneykien
2020-12-04  0:57                 ` Dmitry V. Levin
2020-12-04  8:39               ` Sergey V Turchin
2020-12-04  8:55       ` Sergey V Turchin
2020-12-04  8:26 ` Sergey V Turchin

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=20201203232451.474b46a7@rigel.localdomain \
    --to=manowar@altlinux.org \
    --cc=devel@lists.altlinux.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

ALT Linux Team development discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
		devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
	public-inbox-index devel

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git