bug-bison
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH 0/3] yacc: compute the best type for the state number


From: Akim Demaille
Subject: Re: [PATCH 0/3] yacc: compute the best type for the state number
Date: Thu, 3 Oct 2019 22:15:50 +0200

Hi Paul,

> Le 3 oct. 2019 à 20:20, Paul Eggert <address@hidden> a écrit :
> 
> On 10/2/19 11:28 PM, Akim Demaille wrote:
> 
>> But I see you already pushed it, although there are things I would have 
>> liked to discuss first.  Also, we now have failures in the history of master 
>> and maint, which I strive to avoid.  And the CI is red currently.
> 
> Sorry, I'm so rusty at Bison development I did not know the current rules. 
> What CI is that? I don't see it mentioned in 
> <https://www.gnu.org/software/bison/> or in 
> <https://savannah.gnu.org/projects/bison/>; should it be?

Well...  It's not very compliant with the FSF policies, so I run it on my own:

- I keep a public repo on GitHub where I push my experiments and where push -f 
is authorized.  That's https://github.com/akimd/bison.
- In the repo, there is a .travis.yml: this is the CI I use, and it's publicly 
visible here: https://travis-ci.org/akimd/bison/builds
- In particular, our current failures: 
https://travis-ci.org/akimd/bison/builds/592926523
- Unfortunately, because I use "secrets" only my own jobs are run on the CI 
(otherwise one could easily change .travis.yml to display the secrets and just 
read them in the logs).

I don't have much time right now, I'll continue tomorrow in the morning.

Cheers!


reply via email to

[Prev in Thread] Current Thread [Next in Thread]