|
From: | Thomas Huth |
Subject: | Re: [RFC PATCH 2/2] gitlab-ci: Add a job building TCI with Clang |
Date: | Thu, 21 Jan 2021 11:08:29 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 |
On 10/01/2021 17.27, Philippe Mathieu-Daudé wrote:
Split the current GCC build-tci job in 2, and use Clang compiler in the new job. Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org> --- RFC in case someone have better idea to optimize can respin this patch. .gitlab-ci.yml | 22 ++++++++++++++++++++-- 1 file changed, 20 insertions(+), 2 deletions(-)
I'm not quite sure whether we should go down this road ... if we wanted to have full test coverage for clang, we'd need to duplicate *all* jobs to run them once with gcc and once with clang. And that would be just overkill.
I think we already catch most clang-related problems with the clang jobs that we already have in our CI, so problems like the ones that you've tried to address here should be very, very rare. So I'd rather vote for not splitting the job here.
Thomas
[Prev in Thread] | Current Thread | [Next in Thread] |