Recently Elyezer was talking about a possible workaround for automation.
On Thu, Apr 26, 2018 at 10:29 AM, Jeremy Audet wrote:
> +1 to switching away from SQLite. I've often pondered a failed test and
> wondered "is this a genuine bug, or a side-effect of using SQLite?" This
egration test suite?
Also, looking at
https://docs.pulpproject.org/en/3.0/nightly/contributing/continuous_integration.html
"The unit tests for both pulpcore and pulpcore-plugin live in the tests
<https://github.com/pulp/pulp/blob/3.0-dev/tests/> folder"
The link seems to rendering a
"The plan for quality involves the continuous delivery of Pulp 3 where both
unit and integration are run with each PR and prior to each release to PyPI"
My concern about the above statement is that as the number of tests
increases, the time it will take to run the pulp-smash integration suite
On Wed, Mar 7, 2018 at 8:58 AM, Robin Chan wrote:
> I would like to hear from QE since I know they had some concerns here.
> Since the Pulp QE team is much smaller, having to manage attendance to
> multiple traige's per week is more of a strain on them to have the
>
On Fri, Dec 15, 2017 at 4:23 PM, Bryan Kearney wrote:
> On 12/12/2017 11:47 AM, Brian Bouterse wrote:
> >
> > - Lazy downloading. I think this should be a top 3.1 priority. It will
> > take a significant effort to update/test/release the streamer so I don't
> > think we can
+1
On Tue, Nov 21, 2017 at 7:51 AM, David Davis wrote:
> +1
>
>
> David
>
> On Mon, Nov 20, 2017 at 10:58 PM, Daniel Alley wrote:
>
>> +1
>>
>> On Mon, Nov 20, 2017 at 9:24 AM, Ina Panova wrote:
>>
>>> +1
>>>
>>>
>>>
>>>
On Fri, Nov 10, 2017 at 11:59 AM, Patrick Creech wrote:
> On Fri, 2017-11-10 at 11:35 -0500, Jeremy Audet wrote:
> > > > Hosting packages in just one place is simpler than hosting packages
> in multiple places.
> > > > There's
> > > > less room for error when the simpler
On Fri, Nov 10, 2017 at 11:35 AM, Jeremy Audet wrote:
> Hosting packages in just one place is simpler than hosting packages in
>>> multiple places. There's
>>> less room for error when the simpler thing is done.
>>>
>>
>> It shouldn't be too hard to set up.
>>
>
> Fair enough.
On Fri, Nov 10, 2017 at 10:43 AM, Patrick Creech wrote:
> On Fri, 2017-11-10 at 10:26 -0500, Jeremy Audet wrote:
> > On Thu, Nov 9, 2017 at 4:58 PM, Patrick Creech
> wrote:
> > > As part of the ongoing release engineer changes, I would like to
> propose
On Wed, Nov 23, 2016 at 11:46 AM, Og Maciel wrote:
> I **really** love the new logo!!!
>
+1
>
> On Wed, Nov 23, 2016 at 11:14 AM, Ina Panova wrote:
>
>> Team,
>>
>> take a look at the changes that have been done [0]:
>>
>> - leaves are a bit shrunk, so
This week's report
https://pulp.plan.io/projects/pulp/wiki/Bug_Trends_Report_2016-09-16
Please let me know if you have any questions, comments or feedback. Also
please provide any suggestion on what other information would be useful in
the report.
Previous week's reports
This week's report
https://pulp.plan.io/projects/pulp/wiki/Bug_Trends_Report_2016-09-09
Please let me know if you have any questions, comments or feedback. Also
please provide any suggestion on what other information would be useful in
the report.
Previous week's reports
>
> Michael
>
> On Thu, Sep 8, 2016 at 10:50 AM, Preethi Thomas <ptho...@redhat.com>
> wrote:
>
>> They are running, but sometimes we do have to manually trigger them.
>>
>> Here is the latest run ( on September 5)
>> https://pulp-jenkins.rhev-ci-vms.eng.rd
13 matches
Mail list logo