Interop testing: run the autopkgtest suite against presswork (Rust cupsd reimplementation)

Open
#802 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
22/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
c, github-actions, rust, shell
Domain
devops, testing-qa

Research direction

The proposal touches ci/ci-setup.sh and the CI matrix, and asks whether the downstream autopkgtests spawn a live cupsd at all. Before any CI work, a maintainer must answer that question and choose between an experimental matrix entry and a separate workflow file. Done means that decision is recorded here and an agreed experimental leg exists; the issue is not ready for a newcomer until then.

Written by the indexing model from the issue text.

Description

Hi - I'm the author of presswork, a drop-in replacement for the CUPS 2.x scheduler/daemon written in Rust (Apache-2.0 OR MIT). Same IPP wire protocol, cupsd.conf/printers.conf parsing, spool layout, and filter/backend contract. Upstream ipptool matrix passes 34/0/1 and the upstream test/5.x client suite passes 34/34.

Proposal: add an experimental CI leg that runs cups-filters' downstream autopkgtests with presswork as the daemon instead of the distro cupsd (the build axis still uses libcups as today - presswork only replaces the daemon). This would exercise the filter/backend contract against a second, independent scheduler implementation, and any divergences found are equally useful to both projects - bugs on our side get fixed, underspecified behavior gets documented.

Happy to do the work and open a PR against ci/ci-setup.sh + the matrix. Before I send it, two questions so I shape it correctly:

  1. Do the autopkgtests currently spawn/connect a live cupsd, or are they daemon-free? (i.e., is there actually a daemon axis to swap?)
  2. Preferred delivery: experimental matrix entry (continue-on-error) vs a separate workflow file?

Install is one line (curl-pipe installer, .deb, or ghcr.io/vindeckyy/presswork:latest image). No objection if this is out of scope - just figured mutual interop coverage was worth offering.

Dominant language
C
Stars
202
Forks
161
Avg merge
14h 4m
Merged PRs (30d)
34

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenPrinting/cups-filters

All issues in OpenPrinting/cups-filters

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.