Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cirrus: Update FreeBSD support #7592

Closed

Conversation

@danielgustafsson
Copy link
Member

@danielgustafsson danielgustafsson commented Aug 19, 2021

This adds a FreeBSD 13.0 build to the matrix, and moves the sanitizer over to 12.2 as the 12.1 build has been removed.

@danielgustafsson
Copy link
Member Author

@danielgustafsson danielgustafsson commented Aug 20, 2021

Perhaps name: FreeBSD 13.0 ?

Doh, of course.

@jay jay added the CI label Aug 21, 2021
@bagder
Copy link
Member

@bagder bagder commented Aug 22, 2021

The FreeBSD 12.2 timeout is really strange. It seems to be doing nothing...

@jay
Copy link
Member

@jay jay commented Aug 22, 2021

I don't see any CI checks associated with these commits for some reason.

edit: Nevermind, though it is not showing by the individual commits it does show in the checks tab. I requested 12.2 to be re-run.

@danielgustafsson
Copy link
Member Author

@danielgustafsson danielgustafsson commented Aug 23, 2021

The FreeBSD 12.2 timeout is really strange. It seems to be doing nothing...

It's incredibly puzzling, the CPU and memory graphs on the Cirrus page are also flatlined. It seems that the address sanitizer runtime isn't really working too well with our test harness on FreeBSD 12.2

@mback2k
Copy link
Member

@mback2k mback2k commented Aug 28, 2021

Maybe do the FreeBSD 12 change in a separate commit/PR to move forward with testing FreeBSD 13?

@danielgustafsson
Copy link
Member Author

@danielgustafsson danielgustafsson commented Aug 28, 2021

As alluded to the in the now removed comment, a 13.0 image became
available and is now ready to be used.

The sanitizer builds were running on the 12.1 image which since has
been removed from the config, leaving the builds not running at all.
When enabled it turns out that they don't actually work due to very
long timeouts in executing the tests, so keep the disabled for now
but a bit more controlled.
@danielgustafsson
Copy link
Member Author

@danielgustafsson danielgustafsson commented Sep 7, 2021

The FreeBSD builds now succeeded so unless there are objections I will go ahead with this minimal patch to bump our CI coverage for FreeBSD.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

4 participants