Interop testing: run the autopkgtest suite against presswork (Rust cupsd reimplementation)
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
- 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:
- Do the autopkgtests currently spawn/connect a live cupsd, or are they daemon-free? (i.e., is there actually a daemon axis to swap?)
- 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
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OpenPrinting/cups-filters
-
Division by zeroOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
OpenPrinting/cups-filters#689 ·
Maintainers usually reply within 1 day
-
Division by zeroOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
OpenPrinting/cups-filters#688 · 3 reactions ·
Maintainers usually reply within 1 day
-
Missing informationOpen
Difficulty 1/5 Under an hour Newbie friendliness 85/100
OpenPrinting/cups-filters#546 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
OpenPrinting/cups-filters#539 · 21 comments ·
Maintainers usually reply within 1 day
-
print-color-mode=monochrome is ignored for PPDs whose ColorModel gray choice is "Grayscale" (Foomatic)May be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
OpenPrinting/cups-filters#801 · 2 comments ·
Maintainers usually reply within 1 day
All issues in OpenPrinting/cups-filters
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ChupathingyCE/chupathingyce#1550 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
redis/redis#16302 · 1 comment ·
Maintainers usually reply within 1 day
-
slice
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Life-Framework/Life-Framework#3878 ·
Maintainers usually reply within 1 day
-
`sha256()` returns a wrong hash when libsql-ffi is built with gcc 11 or laterPossibly taken @colinhacks claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
tursodatabase/libsql#2333 ·
Maintainers usually reply within 11 days