Status/2025Q3/sta-wpc-ci-automation.adoc: Add report #549
+111
−0
Conversation
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
lsalvadore
suggested changes
Oct 5, 2025
|
|
||
| ==== /tests/ci improvements | ||
|
|
||
| The /tests/ci subdirectory of the src tree was introduced in link:https://cgit.freebsd.org/src/commit/?id=cb9d4bb1fbb9ac0eb9f211656e91f9d5254c166c[commit: Add preliminary in-tree CI infrastructure for developers] by bofh@ and aims to provide an easy way for developers to replicate the CI testing run by link:https://ci.freebsd.org[our Jenkins cluster]. In this quarter, the following improvements were made by the team: |
There was a problem hiding this comment.
I suggest using the mailto macro.
Also, are you sure you want /tests/ci instead of tests/ci? You use the second alternative more times than the first in this report.
Suggested change
| The /tests/ci subdirectory of the src tree was introduced in link:https://cgit.freebsd.org/src/commit/?id=cb9d4bb1fbb9ac0eb9f211656e91f9d5254c166c[commit: Add preliminary in-tree CI infrastructure for developers] by bofh@ and aims to provide an easy way for developers to replicate the CI testing run by link:https://ci.freebsd.org[our Jenkins cluster]. In this quarter, the following improvements were made by the team: | |
| The tests/ci subdirectory of the src tree was introduced in link:https://cgit.freebsd.org/src/commit/?id=cb9d4bb1fbb9ac0eb9f211656e91f9d5254c166c[commit: Add preliminary in-tree CI infrastructure for developers] by mailto:bofh@FreeBSD.org[Muhammad Moinur Rahman] and aims to provide an easy way for developers to replicate the CI testing run by link:https://ci.freebsd.org[our Jenkins cluster]. In this quarter, the following improvements were made by the team: |
|
|
||
| ==== Test case management | ||
|
|
||
| Since the last quarter, link:https://ci.freebsd.org/tinderbox[Tinderbox] has been reporting that our supported platforms are failing in CI since a link:https://ci.freebsd.org/job/FreeBSD-main-amd64-test/26756/[run from the last quarter]. As the backlog grows larger, it becomes harder for users and developers to notice a new failure and pin a failure to a particular commit. |
There was a problem hiding this comment.
"Since the last quarter" is said twice
Suggested change
| Since the last quarter, link:https://ci.freebsd.org/tinderbox[Tinderbox] has been reporting that our supported platforms are failing in CI since a link:https://ci.freebsd.org/job/FreeBSD-main-amd64-test/26756/[run from the last quarter]. As the backlog grows larger, it becomes harder for users and developers to notice a new failure and pin a failure to a particular commit. | |
| link:https://ci.freebsd.org/tinderbox[Tinderbox] has been reporting that our supported platforms are failing in CI since a link:https://ci.freebsd.org/job/FreeBSD-main-amd64-test/26756/[run from the last quarter]. As the backlog grows larger, it becomes harder for users and developers to notice a new failure and pin a failure to a particular commit. |
|
|
||
| Since the last quarter, link:https://ci.freebsd.org/tinderbox[Tinderbox] has been reporting that our supported platforms are failing in CI since a link:https://ci.freebsd.org/job/FreeBSD-main-amd64-test/26756/[run from the last quarter]. As the backlog grows larger, it becomes harder for users and developers to notice a new failure and pin a failure to a particular commit. | ||
|
|
||
| To complement the /tests/ci CI/CD automation improvements, along with link:https://github.com/markjdb/bricoler[Bricoler] to help with more granular investigations, I worked on cleaning up the failing test backlog on tier-1 architectures. The following patches and bug reports were submitted as a result of this (still ongoing) work: |
There was a problem hiding this comment.
We have a macro for filenames too. Again, are you sure what you want is /tests/ci and not tests/ci?
Suggested change
| To complement the /tests/ci CI/CD automation improvements, along with link:https://github.com/markjdb/bricoler[Bricoler] to help with more granular investigations, I worked on cleaning up the failing test backlog on tier-1 architectures. The following patches and bug reports were submitted as a result of this (still ongoing) work: | |
| To complement the [.filename]#tests/ci# CI/CD automation improvements, along with link:https://github.com/markjdb/bricoler[Bricoler] to help with more granular investigations, I worked on cleaning up the failing test backlog on tier-1 architectures. The following patches and bug reports were submitted as a result of this (still ongoing) work: |
|
|
||
| To catch errors more quickly, instead of relying on link:https://ci.freebsd.org[Jenkins] to update the test report, I ran local CI multiple times daily. To help with this, I worked on some tooling to speed up the testing/debugging cycles. I am maintaining the following (currently uncommitted) tools: | ||
|
|
||
| * link:https://codeberg.org/svmhdvn/mypoudriere/src/branch/main/myfreebsd[parallel CI runner built on top of /tests/ci] |
There was a problem hiding this comment.
Same question as above about /tests/ci instead of tests/ci
svmhdvn
force-pushed
the
q3statusreport
branch
from
5957d70 to
0779e49
Compare
|
Thanks for the feedback, made the requested changes in v2. Anything else needed? |
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.
No description provided.