Skip to Content
  2. Mailing Lists
  3. Contributors
  4. Re: Issues with Travis

Archives

Contributors

Re: Issues with Travis

Re: Issues with Travis

Re: Issues with Travis 

> - a minimalist GitHub

> action that orchestrates the thing ( example a in Shopinvader repo [5] )

> It's lean, seems to work well and is pretty fast, as the installation step

> is reduced to the minimum (i.e. downloading the docker image).

this I think is the killer feature. And as you describe the transition period 
below, we'll have enough time to iron out corner cases; preserving the amount 
of work we put into this was my main reason to try to salvage current MQT


> In terms of

> the general mechanics, I have only one open question: can we rely on the

> Odoo exit code to detect test failure or do we still need a log parser ?

the exit code is trustworthy to my knowledge
https://github.com/OCA/OCB/blob/14.0/odoo/service/server.py#L1229
and similar code exists more or less forever already. Isn't the log parsing 
done by runbot to also error out on warnings and give early notice when it 
fails?


> If people agree

sounds perfectly fine to me


> - think about older

> branches: the concept will work, I'm sure (I've tested 10, 12, 13, 14 and 8

> should work too), but the deployment has to be organized

I personally am not willing to invest work in the py2 versions, but don't see 
a reason why others shouldn't work on this.


-- 
Your partner for the hard Odoo problems
https://hunki-enterprises.com
by Holger Brunn - 06:21 - 22 Feb 2021

1 attachments 1 attachments

signature.asc

Reference

  • Issues with Travis
    Hi,
     
    I have been checking that lately Travis is getting slower to start a job. After checking, I think the problem is that travis has less available jobs, as you can check on https://www.traviscistatus.com/#day. I am not sure if this is a strategy for them or just a complication, but it seems consistent in the last month. For example, yesterday, there were 9.091 jobs at 7:40 on backlog and it took 6 hours to stay without backlog. I am not sure how much time took a job on backlog, but I am pretty sure it could be waiting two or three. Obviously, this kind of problems are annoying, as merging a PR can takes hours (and I cannot imagine what happens if we try to merge two PRs on the same branch).
     
    In order to avoid this problem, today I was able to use Github Actions with minor changes on maintainer-quality-tools.
     
    Has anyone tried to do something on this line? Has OCA checked other options?
     
    Kind regards,
     
    Enric Tobella Alomar
    etobella@creublanca.es
     
    Centros Médicos Creu Blanca
    Tel: 902 202 230
     
    Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
    pueden contener información reservada y/o confidencial, destinada exclusivamente
    para el uso del destinatario o la persona responsable de entregarlo al mismo,
    estando su uso no autorizado prohibido legalmente.
    Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
    salvo ratificación escrita por ambas partes. En caso de su recepción por error,
    rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
    o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
    a su eliminación.




    Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
    pueden contener información reservada y/o confidencial, destinada exclusivamente
    para el uso del destinatario o la persona responsable de entregarlo al mismo,
    estando su uso no autorizado prohibido legalmente.
    Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
    salvo ratificación escrita por ambas partes. En caso de su recepción por error,
    rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
    o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
    a su eliminación.
    by Enric Tobella Alomar - 07:00 - 22 Oct 2020