Philippe Mathieu-Daudé writes:
> On 4/11/22 07:27, Thomas Huth wrote:
>> On 03/11/2022 22.23, Stefan Hajnoczi wrote:
>>> GitLab CI times out when the clang-user job takes over 1 hour.
>> Oh, that's new to me ... is that a regression? Has something become
>> slower? Or did we just add more stuff
On 4/11/22 07:27, Thomas Huth wrote:
On 03/11/2022 22.23, Stefan Hajnoczi wrote:
GitLab CI times out when the clang-user job takes over 1 hour.
Oh, that's new to me ... is that a regression? Has something become
slower? Or did we just add more stuff to the user builds recently?
We added mor
On 03/11/2022 22.23, Stefan Hajnoczi wrote:
GitLab CI times out when the clang-user job takes over 1 hour.
Oh, that's new to me ... is that a regression? Has something become slower?
Or did we just add more stuff to the user builds recently?
Anyway, if it's just taking a little bit longer th
On 11/4/22 09:32, Philippe Mathieu-Daudé wrote:
+Richard
On 3/11/22 22:23, Stefan Hajnoczi wrote:
GitLab CI times out when the clang-user job takes over 1 hour. Split it
into parts that check various architectures.
An alternative is to have one job per architecture but that clutters the
pipeli
+Richard
On 3/11/22 22:23, Stefan Hajnoczi wrote:
GitLab CI times out when the clang-user job takes over 1 hour. Split it
into parts that check various architectures.
An alternative is to have one job per architecture but that clutters the
pipeline view and maybe there is some sharing when mult
GitLab CI times out when the clang-user job takes over 1 hour. Split it
into parts that check various architectures.
An alternative is to have one job per architecture but that clutters the
pipeline view and maybe there is some sharing when multiple targets are
built at once.
Signed-off-by: Stefa
