Cirrus-ci-docs: Is Cirrus down?

Created on 25 Apr 2019  路  5Comments  路  Source: cirruslabs/cirrus-ci-docs

We're running CI for https://github.com/CaseyCarter/cmcstl2/pull/291, but jobs 1 and 2 are hanging (they shouldn't take this long to complete and I can't access the logs).

Is this a server-side problem or a client-side problem?

question

Most helpful comment

Glad you found the issue! Shout out to @RDIL! 馃檶

Emails are still the best way to communicate IMO (filters, push notifications) 馃槄

All 5 comments

Most likely an issue within the task. I would try cancelling and rerunning.

Works fine for me, I think it is just your task stuck hanging. Restarting it is probably your best option.

Please email [email protected] next time to get faster response.

I see some logs now. You didn't see the logs probably because there were no new logs and Cirrus only shows new logs in real-time (there is no buffer at the moment). Please follow #138 for updates on this UX issue.

Seems the issue started happening after this commit https://github.com/CaseyCarter/cmcstl2/commit/afdc1691aff91cbd8112de9812e789653884960d and it looks like to be very reproducible even though it passes on version 8 of the compiler. 馃 Do you think it might be related? Seem it always hangs on the following file:

[337/339] : && /usr/bin/g++-7  -O3 -DNDEBUG   test/view/CMakeFiles/span.dir/span.cpp.o  -o test/view/span   && :

Yes, after @RDIL helped me out, I did a bit of digging, and realised that it's definitely an image issue -- apparently Bionic Beaver doesn't ship with GCC 7.4 (despite that having been released months before the image was built).

I've kicked off a Disco Dingo build now, so that will (hopefully) fix the problem when I push it in the next hour or so.

Please email [email protected] next time to get faster response.

Thanks for the email address!

Glad you found the issue! Shout out to @RDIL! 馃檶

Emails are still the best way to communicate IMO (filters, push notifications) 馃槄

Was this page helpful?
0 / 5 - 0 ratings

Related issues

fkorotkov picture fkorotkov  路  4Comments

dotdoom picture dotdoom  路  4Comments

dotdoom picture dotdoom  路  5Comments

plicease picture plicease  路  5Comments

fkorotkov picture fkorotkov  路  5Comments