чт, 23 янв. 2020 г. в 15:20, Willy Tarreau :
> On Wed, Jan 22, 2020 at 11:10:05PM +0100, Tim Düsterhus wrote:
> > > both travis and github actions do offer 4 parallel builds, while
> cirrus and
> > > app veyor offer 1 parallel build.
> >
> > Parallel Builds just improve test speed. I don't conside
чт, 23 янв. 2020 г. в 20:54, Willy Tarreau :
> On Thu, Jan 23, 2020 at 08:40:19PM +0500, ??? wrote:
> > those timeouts are not related to travis itself, I beleive they are
> mostly
> > related to either real failures or tests instability (race condition).
>
> These tests are racy by natur
On Thu, Jan 23, 2020 at 08:40:19PM +0500, ??? wrote:
> those timeouts are not related to travis itself, I beleive they are mostly
> related to either real failures or tests instability (race condition).
These tests are racy by nature and some rely on short delays (i.e. health
checks). If
чт, 23 янв. 2020 г. в 15:20, Willy Tarreau :
> On Wed, Jan 22, 2020 at 11:10:05PM +0100, Tim Düsterhus wrote:
> > > both travis and github actions do offer 4 parallel builds, while
> cirrus and
> > > app veyor offer 1 parallel build.
> >
> > Parallel Builds just improve test speed. I don't conside
On Wed, Jan 22, 2020 at 11:10:05PM +0100, Tim Düsterhus wrote:
> > both travis and github actions do offer 4 parallel builds, while cirrus and
> > app veyor offer 1 parallel build.
>
> Parallel Builds just improve test speed. I don't consider that an
> important selling point for us. The developme
чт, 23 янв. 2020 г. в 03:10, Tim Düsterhus :
> Ilya,
>
> Am 22.01.20 um 23:04 schrieb Илья Шипицин:
> >> Yes, that's my understanding of GitHub actions as well. However I
> >> dislike having three types of CI (Travis, Cirrus and GitHub Actions).
> >> Can Travis be replaced with GitHub Actions for
Ilya,
Am 22.01.20 um 23:04 schrieb Илья Шипицин:
>> Yes, that's my understanding of GitHub actions as well. However I
>> dislike having three types of CI (Travis, Cirrus and GitHub Actions).
>> Can Travis be replaced with GitHub Actions for our use case? I guess
>> Cirrus can't, because FreeBSD?
>
чт, 23 янв. 2020 г. в 02:59, Tim Düsterhus :
> Ilya,
>
> Am 22.01.20 um 22:41 schrieb Илья Шипицин:
> > let us move it to Github Actions.
> > as far as I tried no extra step are required for enabling, just proper
> file
> > in
> >
> > .github/workflows
>
> Yes, that's my understanding of GitHub ac
Willy,
Ilya,
Am 22.01.20 um 22:52 schrieb Willy Tarreau:
> OK, why not, let's give it a try. Now applied, thanks!
> Willy
>
Appears to work fine: https://github.com/haproxy/haproxy/runs/403976092
However see my sibling email, please.
Best regards
Tim Düsterhus
Ilya,
Am 22.01.20 um 22:41 schrieb Илья Шипицин:
> let us move it to Github Actions.
> as far as I tried no extra step are required for enabling, just proper file
> in
>
> .github/workflows
Yes, that's my understanding of GitHub actions as well. However I
dislike having three types of CI (Travis
On Wed, Jan 22, 2020 at 10:52:28PM +0100, Willy Tarreau wrote:
> Hi Ilya,
>
> On Thu, Jan 23, 2020 at 02:41:05AM +0500, ??? wrote:
> > Hello,
> >
> > I spent lots of time trying to get cygwin on travis working.
> > no luck.
> >
> > let us move it to Github Actions.
> > as far as I tried
Hi Ilya,
On Thu, Jan 23, 2020 at 02:41:05AM +0500, ??? wrote:
> Hello,
>
> I spent lots of time trying to get cygwin on travis working.
> no luck.
>
> let us move it to Github Actions.
> as far as I tried no extra step are required for enabling, just proper file
> in
>
> .github/workfl
Hello,
I spent lots of time trying to get cygwin on travis working.
no luck.
let us move it to Github Actions.
as far as I tried no extra step are required for enabling, just proper file
in
.github/workflows
(attached in patch).
Cheers,
Ilya Shipitcin
From 372c547a94ff02fa04ca052a87863161d3e8
13 matches
Mail list logo
