Re: [pytest-dev] pytest slack reporting plugin proposal

2019-05-02 Thread Floris Bruynooghe
Great, that all seems to have worked quickly. Thanks for improving the pytest ecosystem! On Thu 02 May 2019 at 21:52 +0300, Arseniy Antonov wrote: > Thanks! > > Will do it in 1 day. > Also, GitHub is pretty friendly and routes all requests after transferring > to the new URL. > > > > > чт, 2 мая

Re: [pytest-dev] pytest slack reporting plugin proposal

2019-05-02 Thread Arseniy Antonov
Thanks! Will do it in 1 day. Also, GitHub is pretty friendly and routes all requests after transferring to the new URL. чт, 2 мая 2019 г. в 21:49, Bruno Oliveira : > > On Thu, May 2, 2019 at 3:45 PM Arseniy Antonov > wrote: > >> I've initialized transfer process to you (Bruno) >> And added y

Re: [pytest-dev] pytest slack reporting plugin proposal

2019-05-02 Thread Bruno Oliveira
On Thu, May 2, 2019 at 3:45 PM Arseniy Antonov wrote: > I've initialized transfer process to you (Bruno) > And added you and Floris as a maintainer in PyPi. > Thanks Anseniy, I have completed the transfer, everything should be in place (let me know otherwise). The next step is probably to upda

Re: [pytest-dev] pytest slack reporting plugin proposal

2019-05-02 Thread Arseniy Antonov
I've initialized transfer process to you (Bruno) And added you and Floris as a maintainer in PyPi. чт, 2 мая 2019 г. в 21:38, Bruno Oliveira : > Hi everyone > > On Thu, May 2, 2019 at 3:27 PM Arseniy Antonov > wrote: > >> >> Please tell me what I should do next by the process. >> > > Thanks Arse

Re: [pytest-dev] pytest slack reporting plugin proposal

2019-05-02 Thread Bruno Oliveira
Hi everyone On Thu, May 2, 2019 at 3:27 PM Arseniy Antonov wrote: > > Please tell me what I should do next by the process. > Thanks Arseniy for the interest. The steps are written here: https://github.com/pytest-dev/pytest/blob/master/CONTRIBUTING.rst#submitting-plugins-to-pytest-dev Mainly

Re: [pytest-dev] pytest slack reporting plugin proposal

2019-05-02 Thread Arseniy Antonov
Hi > If you want to maintain your plugin under pytest-dev I think that should > be fine as long as [0] is followed. That's exactly what I want. Please tell me what I should do next by the process. чт, 2 мая 2019 г. в 20:44, Floris Bruynooghe : > Hi Arseniy, Ronny, > > If you want to maintain you

Re: [pytest-dev] pytest slack reporting plugin proposal

2019-05-02 Thread Floris Bruynooghe
Hi Arseniy, Ronny, If you want to maintain your plugin under pytest-dev I think that should be fine as long as [0] is followed. While indeed this doesn't mean you'll magically have other maintainers it doesn't seem like that's what you're after. So as long as the requirements are met this is pro

Re: [pytest-dev] [core] Tidelift Funding

2019-05-02 Thread Floris Bruynooghe
Hi Bruno, On Wed 01 May 2019 at 17:25 -0300, Bruno Oliveira wrote: > So my question is: how do the core maintainers feel about pytest joining > Tidelift? Thanks for the wait-and-see approach taken, I likewise have shifted my opinion on this from some scepticism to mostly positive. So if there's

Re: [pytest-dev] Keeping failing test ids for git bisect

2019-05-02 Thread nicoddemus
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Florians, > Any hints on which hooks would be most useful for gathering the failing tests (or maybe a hint for existing code to look at)? Then I might write that plugin :) I suggest to take a look at the implementation of the LFPlugin, which use

Re: [pytest-dev] [core] Tidelift Funding

2019-05-02 Thread nicoddemus
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 > Only thought from my side — please, just make sure there's "way back", in case reality will not match your expectations. Indeed that's a very important aspect, here's the section of the agreement[1] regarding that: - --- 6.2 How and when can this

Re: [pytest-dev] Keeping failing test ids for git bisect

2019-05-02 Thread Florian Schulze
On 2 May 2019, at 11:28, Florian Bruhin wrote: Hey, On Thu, May 02, 2019 at 11:22:08AM +0200, Florian Schulze wrote: Is there a way to run a bunch of tests like with --lf but don't clear the cache when they pass? This would be mighty helpful for git bisect. For now I helped myself by copying t

Re: [pytest-dev] Keeping failing test ids for git bisect

2019-05-02 Thread Florian Bruhin
Hey, On Thu, May 02, 2019 at 11:22:08AM +0200, Florian Schulze wrote: > Is there a way to run a bunch of tests like with --lf but don't clear > the cache when they pass? This would be mighty helpful for git bisect. > For now I helped myself by copying the test ids, but that requires > editing the

[pytest-dev] Keeping failing test ids for git bisect

2019-05-02 Thread Florian Schulze
Hi! Is there a way to run a bunch of tests like with --lf but don't clear the cache when they pass? This would be mighty helpful for git bisect. For now I helped myself by copying the test ids, but that requires editing the list copied from the terminal before being able to paste them to the comm

Re: [pytest-dev] [core] Tidelift Funding

2019-05-02 Thread Bruno Oliveira
Em qui, 2 de mai de 2019 04:44, Florian Bruhin escreveu: > Hey, > > On Wed, May 01, 2019 at 05:25:58PM -0300, Bruno Oliveira wrote: > > there were no obligations whatsoever after joining the platform other > than > > "maintain the project", which they were already doing anyway. There's no > > obl

Re: [pytest-dev] [core] Tidelift Funding

2019-05-02 Thread Florian Bruhin
Hey, On Wed, May 01, 2019 at 05:25:58PM -0300, Bruno Oliveira wrote: > there were no obligations whatsoever after joining the platform other than > "maintain the project", which they were already doing anyway. There's no > obligation to market the platform in anyway as well (say, being forced to >

Re: [pytest-dev] Adding a marker to items that have a fixture

2019-05-02 Thread Florian Bruhin
On Thu, May 02, 2019 at 02:18:42PM +1200, Craig de Stigter wrote: > This sort of works ( the marker is present by the time the test runs), but > command-line filtering options (`-m 'not solr'`) don't filter based on it. > I guess this hook is running after those options have been consulted? > > I