Skip to Content.
Sympa Menu

freetds - Re: [freetds] Appveyor Builds & Testing

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: Ramiro Morales <cramm0 AT gmail.com>
  • To: Frediano Ziglio <freddy77 AT gmail.com>
  • Cc: FreeTDS Development Group <freetds AT lists.ibiblio.org>, pymssql-ml <pymssql AT googlegroups.com>
  • Subject: Re: [freetds] Appveyor Builds & Testing
  • Date: Sun, 26 Jul 2015 13:37:45 -0300

On Fri, Jul 24, 2015 at 2:03 PM, Frediano Ziglio <freddy77 AT gmail.com> wrote:
> 2015-07-22 12:25 GMT+01:00 Ramiro Morales <cramm0 AT gmail.com>:
ill be merged.
>
>> This causes for example that once a regression occurs there is no
>> granularity to know which of the intermediate commit (between the
>> merges/rebases) is the culprit. See item 5 above for an example.
>>
>
> Not clear here what you mean.
>

What I tried to say was that in the
manual-merge-from-master-from-time-to-time setup it was hard to spot
the individual commit that introduced a build error/test regression
because in that case Appveyor performed only one build with the
changes of all intermediate commits.

But you've fixed this and Appveyor already is bulding from master.

--
Ramiro Morales
@ramiromorales




Archive powered by MHonArc 2.6.24.

Top of Page