public inbox for linux-safety@lists.elisa.tech
 help / color / mirror / Atom feed
From: "Sudip Mukherjee" <sudip.mukherjee@codethink.co.uk>
To: Paul Albertella <paul.albertella@codethink.co.uk>,
	linux-safety@lists.elisa.tech
Subject: Re: [linux-safety] ci pipeline for clang-analyzer
Date: Thu, 8 Oct 2020 09:44:53 +0100	[thread overview]
Message-ID: <295e221e-215e-6237-3887-238deb63f419@codethink.co.uk> (raw)
In-Reply-To: <9bb53fa2-0f87-c80d-8d11-bbb4caed9400@codethink.co.uk>

Hi Paul,

On 08/10/2020 09:15, Paul Albertella wrote:
> This is great Sudip!
> 
> I see that Travis CI has a max duration of 120 minutes for jobs. If we
> continue tinyconfig, then I'm guessing that should be enough, but we
> will want to explore other options for when we work on more
> representative configs, which I think Elana is planning to define as
> part of the Dev Process WG's work this quarter.
Travis actually has 50 minutes timeout. I have an extended 120 minutes
because of something else I used to do earlier. Actually, going through
my old mails I can see that I should have 180 minutes. Need to check
with them today.
I have also tried with gitlab shared runners which had a 180 minutes
timeout but that has also failed.
https://gitlab.com/sudipm/linux-next/-/jobs/777289423

> 
> Another alternative would be to use Github Actions, which doesn't seem
> to have a maximum job duration, but does limit job runtime to 2000 hours
> per month for a free account.

I will have a look at it today after adding the report generator to my
scripts. If it is 2000 hours per month then we get around 100 hours per
day, which should be more than enough.


-- 
Regards
Sudip

      reply	other threads:[~2020-10-08  8:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <163BD2875A09B377.24414@lists.elisa.tech>
2020-10-07 22:18 ` [linux-safety] ci pipeline for clang-analyzer Sudip Mukherjee
2020-10-08  8:15   ` Paul Albertella
2020-10-08  8:44     ` Sudip Mukherjee [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=295e221e-215e-6237-3887-238deb63f419@codethink.co.uk \
    --to=sudip.mukherjee@codethink.co.uk \
    --cc=linux-safety@lists.elisa.tech \
    --cc=paul.albertella@codethink.co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox