Hi all,
  Someone on LLVM-dev@ mentioned a CI provider that I did not yet know: CircleCI.
For open-source projects, they offer 4 free Linux containers.
Travis is filling up a little, I think, so we could offload some builds to CircleCI.

cheers,
  Johan

On Monday, 14 March 2016 at 09:41:16 UTC, Johan Engelen wrote:
> Hi all,
>   Someone on LLVM-dev@ mentioned a CI provider that I did not yet know: CircleCI.
> For open-source projects, they offer 4 free Linux containers.
> Travis is filling up a little, I think, so we could offload some builds to CircleCI.
>
> cheers,
>   Johan

Hi Johan,

if you have time then just create a configuration for Circle-CI. :-)

It is always worth testing with another environment, especially if there are differences (e.g. newer Ubuntu version or other distribution, LLVM from distribution instead of external source, etc.)

Regards,
Kai

On Tuesday, 15 March 2016 at 17:14:33 UTC, Kai Nacke wrote:
> On Monday, 14 March 2016 at 09:41:16 UTC, Johan Engelen wrote:
>> Hi all,
>>   Someone on LLVM-dev@ mentioned a CI provider that I did not yet know: CircleCI.
>> For open-source projects, they offer 4 free Linux containers.
>> Travis is filling up a little, I think, so we could offload some builds to CircleCI.
>>
>> cheers,
>>   Johan
>
> Hi Johan,
>
> if you have time then just create a configuration for Circle-CI. :-)

OK.

I just read this: "Often the best way to troubleshoot problems is to SSH into a running or finished build to look at log files, running processes, and so on. This will grant you ssh access to the build's containers, prevent the deploy step from starting, and keep the build up for 30 minutes after it finishes to give you time to investigate."
interesting!

I briefly look at CircleCI, but stopped at the point where I had to make our own circle.yml file (of course). Didn't realize it was already reporting back to Github about "failing" builds. Sorry for the annoyance.

On Friday, 18 March 2016 at 10:27:27 UTC, Johan Engelen wrote:
> I briefly look at CircleCI, but stopped at the point where I had to make our own circle.yml file (of course). Didn't realize it was already reporting back to Github about "failing" builds. Sorry for the annoyance.

I created a circle.yml file and enabled Circle-CI again.

To add value a different setup is tested. OS is Ubuntu 14.04 Trusty and the used compiler is clang 3.8. The build is not yet green - it shows an assertion failure in std.math which I also discovered on FreeBSD and Solaris. I also tried to enable a multilib build but hit some timeout.

If someone like to go ahead: The test results can be written into an XML file and made available to the Web UI. I left a hint how to do it in the circle.yml file.

Regards,
Kai

On Sunday, 20 March 2016 at 13:06:02 UTC, Kai Nacke wrote:
> I created a circle.yml file and enabled Circle-CI again.

Nice!

On Sunday, 20 March 2016 at 13:06:02 UTC, Kai Nacke wrote:
> On Friday, 18 March 2016 at 10:27:27 UTC, Johan Engelen wrote:
>> I briefly look at CircleCI, but stopped at the point where I had to make our own circle.yml file (of course). Didn't realize it was already reporting back to Github about "failing" builds. Sorry for the annoyance.
>
> I created a circle.yml file and enabled Circle-CI again.
>
> To add value ...

I just SSH'ed into a CircleCI build of master to look into the missing FileCheck issue. It is *great* to be able to go in and look at the build files etc. So much better than trial-and-error commit testing in a PR branch!

On Sunday, 3 April 2016 at 11:38:03 UTC, Johan Engelen wrote:
> On Sunday, 20 March 2016 at 13:06:02 UTC, Kai Nacke wrote:
>> On Friday, 18 March 2016 at 10:27:27 UTC, Johan Engelen wrote:
>>> I briefly look at CircleCI, but stopped at the point where I had to make our own circle.yml file (of course). Didn't realize it was already reporting back to Github about "failing" builds. Sorry for the annoyance.
>>
>> I created a circle.yml file and enabled Circle-CI again.
>>
>> To add value ...
>
> I just SSH'ed into a CircleCI build of master to look into the missing FileCheck issue. It is *great* to be able to go in and look at the build files etc. So much better than trial-and-error commit testing in a PR branch!

Nice to hear that this works. :-)

I updated Circle-CI to use LLVM-3.9.

Regards,
Kai