Skip to content

tests: enable resolute on every desktop test#852

Merged
igorpecovnik merged 2 commits intomainfrom
tests-enable-resolute
Apr 14, 2026
Merged

tests: enable resolute on every desktop test#852
igorpecovnik merged 2 commits intomainfrom
tests-enable-resolute

Conversation

@igorpecovnik
Copy link
Copy Markdown
Member

Summary

resolute (Ubuntu 26.04 LTS) was promoted to supported in armbian/build#9657, and armbian/os#444 added apt.armbian.com coverage for the desktop snap-shim workarounds + vendor apps on resolute. Now exercise the desktop install path on resolute in CI.

test before after
BUDG01.conf trixie:noble trixie:noble:resolute
CINM01.conf bookworm:trixie:noble bookworm:trixie:noble:resolute
DEEP01.conf (same) (same)
ENLI01.conf (same) (same)
GNME01.conf (same) (same)
I3WM01.conf (same) (same)
KDEP01.conf (same) (same)
MATE01.conf (same) (same)
XFCE01.conf (same) (same)
XMON01.conf (same) (same)
KDEN01.conf noble:plucky noble:resolute (plucky eos as of 2026-01-25)

Test plan

  • CI matrix runs each desktop test against resolute and passes
  • No regression on existing release coverage

…EN01)

resolute (Ubuntu 26.04 LTS) just promoted to `supported` in
armbian/build#9657, and apt.armbian.com#444 added apt.armbian.com
coverage for the snap-shim workarounds + vendor desktop apps on
resolute. Time to actually exercise the desktop install path on
resolute in CI.

Add `resolute` to RELEASE in every desktop test (10 of 11 had
`bookworm:trixie:noble`; BUDG01 had only `trixie:noble`).

Also drop `plucky` from KDEN01 — plucky is eos as of 2026-01-25,
no point running tests against an eos release.
@github-actions github-actions Bot added size/small PR with less then 50 lines 05 Milestone: Second quarter release Unit Tests labels Apr 13, 2026
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Apr 13, 2026

Warning

Rate limit exceeded

@igorpecovnik has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 53 minutes and 29 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 53 minutes and 29 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 410946cf-90a8-4a82-9fa9-b46f11d5a431

📥 Commits

Reviewing files that changed from the base of the PR and between 201d172 and 49ba308.

📒 Files selected for processing (1)
  • tests/KDEN01.conf

Walkthrough

This pull request updates the RELEASE configuration variable across 11 test configuration files in the tests/ directory. Most files append :resolute to their existing release version strings (e.g., "bookworm:trixie:noble" becomes "bookworm:trixie:noble:resolute"), while KDEN01.conf replaces its release string from "noble:plucky" to "noble:resolute". No other configuration entries, logic, or control flow in any files are modified.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely summarizes the main change: enabling resolute across all desktop tests by updating RELEASE configuration values.
Description check ✅ Passed The description is directly related to the changeset, explaining the motivation (resolute promotion to supported), the specific changes made to RELEASE values in each test file, and the test plan.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch tests-enable-resolute

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

KDE Neon is hosted at archive.neon.kde.org/testing, a third-party
PPA that lags new Ubuntu LTS releases by months. They have not
yet published a resolute (26.04) snapshot.

Symptom on resolute install:
  E: Package 'neon-desktop' has no installation candidate

The kde-neon.yaml `releases:` block already only lists noble (no
resolute), so the YAML correctly knows resolute is unsupported —
but the test was lying about it. Revert KDEN01 to `noble`-only
until KDE Neon publishes for resolute.

Other DE tests still test resolute (PR remains net-additive for
xfce / gnome / kde-plasma / mate / cinnamon / i3-wm / xmonad /
enlightenment / budgie / deepin).
@igorpecovnik igorpecovnik merged commit 5006e7d into main Apr 14, 2026
9 of 43 checks passed
@igorpecovnik igorpecovnik deleted the tests-enable-resolute branch April 14, 2026 04:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

05 Milestone: Second quarter release size/small PR with less then 50 lines Unit Tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant