GHA/non-native: move BSDs to a single matrix, add DragonFly and Midnight#21681
Closed
vszakats wants to merge 53 commits into
Closed
GHA/non-native: move BSDs to a single matrix, add DragonFly and Midnight#21681vszakats wants to merge 53 commits into
vszakats wants to merge 53 commits into
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
Member
Author
|
As feared, after FreeBSD 15, FreeBSD 14.4 also performs significantly worse than 14.3 did. Before: https://github.com/curl/curl/actions/runs/26112670879/job/76793672788 (Though not as much slower as 15: #20145) https://github.com/curl/curl/actions/runs/26129991098/job/76852712723?pr=21681 Slowdown is minutes in arm64 jobs, and 1-10 seconds in intel. So bumping to 15 for intel. |
Member
Author
|
MidnightBSD's |
vszakats
added a commit
that referenced
this pull request
May 20, 2026
… updates Example: ``` Wed, 20 May 2026 09:51:48 GMT Updating Avalon repository catalogue... Wed, 20 May 2026 09:51:48 GMT pkg: An error occurred while fetching package: No error Wed, 20 May 2026 09:51:48 GMT pkg: An error occurred while fetching package: No error Wed, 20 May 2026 09:51:48 GMT repository Avalon has no meta file, using default settings Wed, 20 May 2026 09:51:48 GMT pkg: An error occurred while fetching package: No error Wed, 20 May 2026 09:51:48 GMT pkg: An error occurred while fetching package: No error Wed, 20 May 2026 09:51:48 GMT pkg: An error occurred while fetching package: No error Wed, 20 May 2026 09:51:48 GMT pkg: An error occurred while fetching package: No error Wed, 20 May 2026 09:51:48 GMT Unable to update repository Avalon Wed, 20 May 2026 09:51:48 GMT Error updating repositories! Wed, 20 May 2026 09:51:48 GMT Error: Process completed with exit code 3. ``` As tested over at libssh2, retrying the install command also does not help, only repeats the same failure. Also: fix whitespace in matrix. Follow-up to b158d1c #21681 Closes #21694
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
bump cross-platform-actions to v1.1.0.
Ref: https://github.com/cross-platform-actions/action/releases/tag/v1.1.0
merge BSD jobs into a single matrix.
split BSD jobs into build steps as used for other platforms.
A new feature of cross-platform-actions v1.1.0.
sync BSD build steps with other platforms.
add DragonFlyBSD and MidnightBSD to the BSD matrix.
New features of cross-platform-actions v1.1.0.
MidnightBSD uses GnuTLS to add variation, also the preinstalled
OpenSSL is too old (v1.1.1w) for curl.
Stick with autotools for DragonFlyBSD; I could not figure out how
to install cmake.
Refs:
https://en.wikipedia.org/wiki/DragonFly_BSD
https://en.wikipedia.org/wiki/MidnightBSD
bump Intel FreeBSD jobs from v14.3 to v15.0.
fix to show
gccin the NetBSD job name.All these saved 50 lines of YAML. The two new jobs take 2m15s each. The
bump to FreeBSD 15 needs and extra minute in total.
Note, the DragonFlyBSD job seems to have reliability issues. If it
remains an issue, I'll comment it out or delete it in a future commit.