- Mailing Lists
- Contributors
- Re: Issues with Travis
Archives
- By thread 1419
-
By date
- August 2019 59
- September 2019 118
- October 2019 165
- November 2019 97
- December 2019 35
- January 2020 58
- February 2020 204
- March 2020 121
- April 2020 172
- May 2020 50
- June 2020 158
- July 2020 85
- August 2020 94
- September 2020 193
- October 2020 277
- November 2020 100
- December 2020 159
- January 2021 38
- February 2021 87
- March 2021 146
- April 2021 73
- May 2021 90
- June 2021 86
- July 2021 123
- August 2021 50
- September 2021 68
- October 2021 66
- November 2021 74
- December 2021 75
- January 2022 98
- February 2022 77
- March 2022 68
- April 2022 31
- May 2022 59
- June 2022 87
- July 2022 141
- August 2022 38
- September 2022 73
- October 2022 152
- November 2022 39
- December 2022 50
- January 2023 93
- February 2023 49
- March 2023 106
- April 2023 47
- May 2023 69
- June 2023 92
- July 2023 64
- August 2023 103
- September 2023 91
- October 2023 101
- November 2023 94
- December 2023 46
- January 2024 75
- February 2024 79
- March 2024 104
- April 2024 63
- May 2024 40
- June 2024 160
- July 2024 80
- August 2024 70
- September 2024 62
- October 2024 121
- November 2024 117
- December 2024 89
- January 2025 59
- February 2025 104
- March 2025 96
- April 2025 107
- May 2025 52
- June 2025 72
- July 2025 60
- August 2025 81
- September 2025 124
- October 2025 63
- November 2025 22
Contributors
Re: Issues with Travis
@enric I think it's a really good idea
+1
Le mar. 15 déc. 2020 à 13:51, Enric Tobella <etobella@creublanca.es> a écrit :
Another option is tu use odoo/odoo on PRs and both on other cases (when merging with ocabot, OCA/OCB will be tested). As easy as doing this:- stage: test if: type != pull_request env: - TESTS=1 ODOO_REPO="OCA/OCB"WDYT?Enric Tobella AlomarCentros Médicos Creu BlancaTel: 902 202 230Tanto 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.From: Raphaël Valyi <rvalyi@akretion.com>
To: "Contributors" <contributors@odoo-community.org>
Date: Tue, 24 Nov 2020 13:36:47 -0000
Subject: Re: Issues with Travis
I got another idea:why not just simply test using Odoo on odd days and on OCB on even days?Given the very low discrepancies between OCB and Odoo today, it could be a nice trade off between detecting OCB regressions and doing half the test load we do today.What do you think? If you think it's a good idea I volunteer to change the test scripts for doing it.On Tue, Nov 24, 2020 at 8:51 AM Raphaël Valyi <rvalyi@akretion.com> wrote:On Tue, Nov 24, 2020, 7:06 AM David Beal <david.beal@akretion.com> wrote:Hi all,[...]If we could reduce these by 2, environmental impact will be reduced by 2Ci tests:- OCB- odooWhat about testing OCB (or Odoo) only once day per week or something like that? (say unless some special variable to force the test is set).I think it is easy to do in the test script and it could probably be an acceptable trade off to detect compatibility issues soon often without doubling the number of builds all the time. What do you think?Raphaël._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe--_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
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.
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by David BEAL - 02:25 - 15 Dec 2020
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 Alomaretobella@creublanca.esCentros Médicos Creu BlancaTel: 902 202 230Tanto 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