ci pipeline for clang-analyzer
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 7 lines · Sudip Mukherjee
Hi All,
I tried to setup a pipeline for clang-analyzer so that all of us interested can get the test result from latest linux-next. The build with "defconfig" timedout but "tinyconfig" does work. You can see the one from next-20201007 at [1].
Quoted 6 lines
Next, I will try to:
1) set up a cron job so that the pipeline starts as soon as linux-next is published
2) set a pipeline for arm64. looks like travis supports arm64.
3) Add the report-generator to the image.
4) Check if I can push the generated report to a github page.
Little bit of manual run, but the report from clang-analyzer for next-20201007 is now available at https://sudipm-mukherjee.github.io
Signature · 2 lines
Regards Sudip
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.
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.
Looking at Github's pricing page (https://github.com/pricing), I think ELISA could qualify for free 'Teams' level account, which would increase this to 3000 hours per month. However, this is the limit for the whole team, not per user, so we might be better off with individual free accounts.
Paul
Quoted 28 lines · Sudip Mukherjee
Quoted 7 lines · Sudip Mukherjee
Hi All,
I tried to setup a pipeline for clang-analyzer so that all of us interested can get the test result from latest linux-next. The build with "defconfig" timedout but "tinyconfig" does work. You can see the one from next-20201007 at [1].
Quoted 6 lines
Next, I will try to:
1) set up a cron job so that the pipeline starts as soon as linux-next is published
2) set a pipeline for arm64. looks like travis supports arm64.
3) Add the report-generator to the image.
4) Check if I can push the generated report to a github page.Little bit of manual run, but the report from clang-analyzer for next-20201007 is now available at https://sudipm-mukherjee.github.io
Hi Paul,
Quoted 7 lines · Paul Albertella
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
Quoted 4 lines
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.
Signature · 2 lines
Regards Sudip