As we have received an external box sponsored by NetActuate we can now
enable the pre-commit tasks to be run in this box.
Once we have enabled this debug if there are any errors and after
confirmation we can enable this for other tasks too.
Sponsored by: NetActuate
Sponsored by: The FreeBSD Foundation
Approved by: emaste, lwhsu
Differential Revision: https://reviews.freebsd.org/D54220
We previously used `PKG_FORMAT: tar` to avoid spending a lot of time in
zstd compression. Instead just set PKG_LEVEL to compression level 1,
which still produces packages that are much smaller than uncompressed
tarballs with only a small penalty in build time.
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D52858
This reverts commit 676d64ee83.
These tests take a combined 3h to run and are consuming our montly
Cirrus-CI credits in short order, before failing.
In the PR markj reports that the failure appeared somewhere between:
good: da64f6e047
bad: b197d2abcb
Unfortunately, even after we find the offending commit and have a fix we
still do not have sufficient monthly compute credit. Disable these
tests for now, pending a solution to both issues.
PR: 289696
Reviewed by: ngie
Differential Revision: https://reviews.freebsd.org/D52618
These CI works were disabled as we had been suppressing build logs for
developers running CI. That has been addressed by adding a new variable
called CIENV. So reenable the tests.
Approved by: lwhsu
Differential Revision: https://reviews.freebsd.org/D51178
Event: Oslo Hackthon 202508
Pre-commit CI task using the FreeBSD internal CI system silences the
build logs. This is hard to decode the actual problem on why a build is
failing without any clue as the buildlogs are removed once the task
fails.
For now disable the tasks using manual trigger_type.
Approved by: emaste (irc)
Currently we do not have pre-commit testing mechanism for our src tree.
We have merged the CI test scripts into base(HEAD only). The plan is to
replace the entire Jenkins scripts with the one from the base system.
Limitations of the scripts:
- Full test does not work as intended like in a local environment. Our
amd64/aarch64/arm64 test requires somewhere near 4+ hours which is not
supported by CIRRUS-CI hosted systems yet as the hard limitation is
120m. But in future we can try to do this using hosted system with
various cloud providers.
- Currently only works with main branch, stable/13 and stable/14 has not
yet been processed. As the scripts are different.
Approved by: lwhsu
Differential Revision: https://reviews.freebsd.org/D36257
The current default image is set to 13.4 which is going to reach EOL
soon so switch the default CI image to 14.
Will be merged into stable/14 only. This has no operational effect on
the build itself.
Approved by: emaste
MFC after: 3 days
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D50110
Most of the matrix options are manually triggered ones but some of those
do not specifically mention them in the name. So add the string
' (manual)` in the name of the jobs for better clarity in the web
interface of cirrus CI.
These are mostly cosmetic changes and have no effects on the build
itself.
Will be merged in all stable versions.
Approved by: emaste
MFC after: 3 days
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D50110
As of commit 439352ac82 Clang/LLVM 18 is the default in-tree compiler.
Follow suit in with the external toolchain package used by Cirrus-CI.
Sponsored by: The FreeBSD Foundation
Work is in progress to import Clang/LLVM 18 as the base system compiler.
llvm18-lite is not yet in the quarterly package set but but will be
available in the not too distant future, and is available for src forks
that switch to latest packages. Add manual llvm18 jobs now so that they
can be used for testing.
Sponsored by: The FreeBSD Foundation
Clang/LLVM 17 is currently the in-tree default compiler, so use it as
the default Cirrus-CI toolchain. Clang/LLVM 18 is coming soon and needs
to be added here, but I ran into trouble with llvm18-lite package
availability so will look at that later.
Reviewed by: dim (earlier), Jose Luis Duran
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D44162
Updated pkg is now in quarterly and there is no need to forcibly
install a specific version.
This reverts commit 1c376684c7.
This reverts commit 3c097b06a7.
Reported by: bapt
Sponsored by: The FreeBSD Foundation
The git checkout it owned by root, but builds are run as "user". git
refuses to operate in such an environment unless the directory is
trusted so make "user" trust it.
Fixes CI after 99b8c0c35b.
Sponsored by: DARPA
Reviewed by: emaste
Differential Revision: https://reviews.freebsd.org/D42903
Since Cirrus Labs is limiting their free usage tier [1], limit CI runs
on pull requests only. Otherwise, we might deplete our monthly quota
within a few days.
Adapt the task amd64-llvm16 to execute on downstream repos or on pull
requests only.
Other alternatives will be further studied.
[1]: https://cirrus-ci.org/blog/2023/07/17/limiting-free-usage-of-cirrus-ci/
The Cirrus-CI log length issue was addressed by commit 5f72ceb2c5
("Cirrus-CI: for *-gcc12, build world with make -s"), and the failure
itself by commit 0c785f0602 ("Fix GoogleTest 1.14.0 import").
This reverts commit 0ed2e7e889.
Reported by: Jose Luis Duran
Sponsored by: The FreeBSD Foundation
The amd64-gcc12 job is failing at present. Unfortunately Cirrus-CI
appears to have a 100MB log limit and we exceed this before the error
is reported. Disable the job for now until we can address the log
length issue.
See also https://github.com/cirruslabs/cirrus-ci-docs/issues/1176.
Sponsored by: The FreeBSD Foundation
With commit e048f78b21 the default tool chain is Clang/LLVM 16, so
follow along in the llvm pkg used by Cirrus-CI.
MFC after: 1 month
Sponsored by: The FreeBSD Foundation
It appears that Cirrus-CI has a 100MB limit for log output, and we
exceed that (!) with the amd64-gcc12 build. Separate world and kernel
build tasks in an attempt to stay below the limit.
This also has the benefit of showing world and kernel build status
separately in the Cirrus-CI UI.
PR: 271903
Sponsored by: The FreeBSD Foundation
This reduces CI cycle time (a small amount).
Suggested by: brooks
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D40136
We want to get GCC coverage via Cirrus-CI, but don't want to trigger
excessive runs across all forks and branches. Create a duplicate gcc12
task to run automatically for freebsd/freebsd-src.
Reviewed by: jhb
Sponsored by: The FreeBSD Foundation
Run makeman and verify that src.conf.5 has been updated if
required and that there are no missing definition files.
Reviewed by: emaste
Sponsored by: DARPA
Differential Revision: https://reviews.freebsd.org/D39682
Run the `make sysent` target and verify that the repo isn't modified
afterwards. This ensures that a pushed branch contains all the
required bits after a change to syscall.master.
Reviewed by: emaste
Sponsored by: DARPA
Differential Revision: https://reviews.freebsd.org/D39680
tools/pkgbase/metalog_reader.lua checks for errors in METALOG (for
pkgbase staging), such as hard links with differing modes, duplicate
entries, etc. Run it as part of the Cirrus-CI job to prevent
regressions.
Reviewed by: manu, imp
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D37521
As of commit 50d7464c3f we use llvm15 as the system toolchain, and
commit eca005d853 added compiler options incompatible with earlier
versions. Switch to llvm15 packages.
Sponsored by: The FreeBSD Foundation
