Skip to content

Qualify CodexUI on Debian riscv64: 13 canary test failures under emulation #121

Open

Description

@VolkerChristian

CodexUI's staging canary compiled successfully on Debian sid riscv64 under qemu-user-static, then failed 13 of 84 selected CTests. Four additional Breeze cases self-skipped. Record these failures for a separate RISC-V qualification task before restoring Debian riscv64 package targets.

Canary: https://github.com/SNodeC/Packages/actions/runs/43676176105
Failing job: https://github.com/SNodeC/Packages/actions/runs/43676176105/job/132700633813
Source: 271d3bd
Environment: debian:sid, linux/riscv64 emulated on ubuntu-24.04, CMake Release, offscreen Qt under Xvfb. The package hook used CODEXUI_TIMING_POLICY=report and excluded the owner-waived twelve conversation-performance cases. Repository test defaults remain strict. Compilation passed; the unit failed during CTest and was not published.

# Test Failing assertion or termination
41 codexui-conversation-virtualization CTest timeout at 20 seconds; no failed assertion was emitted before termination.
56 codexui-application-layout CTest timeout at 15 seconds; no failed assertion was emitted before termination.
63 codexui-inspector-performance-10000-dpr-1 FAILED: Inspector construction, churn, parsing, measurement, and per-frame work stay bounded.
65 codexui-inspector-performance-10000-dpr-1_25 FAILED: Inspector construction, churn, parsing, measurement, and per-frame work stay bounded.
67 codexui-inspector-performance-10000-dpr-1_5 FAILED: Inspector construction, churn, parsing, measurement, and per-frame work stay bounded.
69 codexui-inspector-performance-10000-dpr-2 FAILED: Inspector construction, churn, parsing, measurement, and per-frame work stay bounded.
72 codexui-async-questions-dpr-1 CTest timeout at 20 seconds; no failed assertion was emitted before termination.
73 codexui-async-questions-dpr-1_25 CTest timeout at 20 seconds; no failed assertion was emitted before termination.
74 codexui-async-questions-dpr-1_5 CTest timeout at 20 seconds; no failed assertion was emitted before termination.
75 codexui-async-questions-dpr-2 FAIL async message exposes an accessible Answer action — four occurrences; assertion checks answer && answer->isVisible().
76 codexui-shell-integration CTest timeout at 45 seconds; no failed assertion was emitted before termination.
82 codexmanager CTest timeout at 90 seconds; no failed assertion was emitted before termination.
83 codexmanager-deletion test_live_app_server_blocks_deletion: AssertionError: ValueError not raised at DeleteProfileDataTest.py:102 (self.assertRaises(ValueError)).

All four Inspector cases recorded 124 row constructions and 5823 paints. The existing work.paints <= work.constructions * 32 + 512 assertion permits 4480 paints. Accepted elapsed-time warnings were also present; report mode does not waive the bounded-work assertion.

These are observations under emulation, not an established diagnosis of native RISC-V behavior. The deletion fixture launches /bin/sleep with argv[0]=codex and CODEX_HOME; production detection reads /proc command-line arguments. The async fixture uses fixed 100-ms event-loop spins. Those boundaries need investigation without assuming they explain the failures.

Owner decision: remove debian-*-riscv64 from CodexUI's package declaration for this release. Decision: Qt desktop application; 13 functional test failures under riscv64 emulation, tracked as an issue.

Scope: packaging support changes only; no test removal, assertion relaxation, repository-default change or performance remediation is part of this exclusion. Other products retain all their declared RISC-V targets. Restore the three Debian targets only after qualification passes. Related implementation: #119.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions