Three failure messages the app can show have never been produced by anything #193
Closed
opened 2026-09-02 12:46:07 +00:00 by JMR-dev
·
0 comments
No Branch/Tag Specified
main
fix/102-picker-back-press-overshoot
fix/268-saf-picker-determinism
feat/ogg-vorbis-libvorbis
feat/expedited-conversion-work
fix/gate-cache-in-worktrees
chore/gate-runs-shellcheck
test/publish-delete-arm-real-provider
docs/e8-instrumented-coverage
docs/api37-carrier-count-drift
docs/e7-second-constraint
test/publish-to-a-real-saf-destination
fix/api37-report-match-line
fix/api37-task-snapshot-crash
test/join-failure-message-on-device
docs/e2e-read-findings-e7
test/cancelling-a-running-export
test/reattach-to-a-running-job
test/content-uri-reaches-ffmpeg
fix/launcher-wiring-waits-for-the-pick
fix/cancel-tests-need-a-slower-encode
test/cancelling-a-running-join
test/cancelling-a-running-session
test/notification-cancel-action
test/ffmpeg-progress-is-observed
test/fallback-asserts-the-path
test/flac-and-opus-assert-their-format
docs/e2e-read-findings
docs/wave4-coverage-numbers
fix/injectable-startup-sweep-scope
test/session-outcome-seam
test/launcher-callback-identity
test/theme-follows-system-dark
test/audio-drop-arm
fix/rotation-waits-for-recreation
fix/convert-guards-on-ready
test/retry-save-mime
test/hardware-progress-reaches-workmanager
test/ffprobe-mapping-seam
test/device-codec-enumeration-seam
test/unknown-container-row
test/null-message-fallbacks
test/cancel-reaches-workmanager
docs/coverage-wave3-recovery
test/concat-engine-seam
docs/coverage-wave3
test/mediaprobe-merge-seam
test/adaptive-shell-wiring
test/aac-audio-args
test/notification-progress-text
test/media3-muxer-guard
test/hardware-fallback-and-cancellation
test/unprobeable-join-clip
test/one-branch-outcomes
test/foreground-type-regimes
fix/bound-wedge-diagnostics
docs/coverage-wave2
test/screen-wiring
test/viewmodel-setters
test/join-state-mapping
test/conversion-state-mapping
test/dedupe-user-messages
fix/restore-stack-merges
test/refused-jobs
test/concatworker-failure-arms
test/container-capabilities-audio
test/readspec-enum-fallbacks
test/outputpublisher-seams
test/mediaprobe-track-seam
test/outputpublisher-partial-branches
test/fake-provider-scaffolding
docs/coverage-read-findings
chore/gitignore-kotlin
test/bound-the-hangs
docs/coverage-remeasure
ci/baseline-counter-precision
fix/invalid-suggestion-chip
ci/wedged-leg-report
fix/reattachment-overwrites-pick
test/theme-live-branches
fix/failed-save-retry
fix/empty-composition-crash
ci/advisory-failure-report
docs/seven-run-counts
test/release-permission-guard
ci/build-workflow-permissions
docs/api37-point-release
docs/benchmark-populate-path
fix/dead-assertion-probe-test
ci/actionlint
test/device-codecs-encode-consequence
fix/sdkmanager-pipefail
docs/readme-restart-claim
fix/saf-picker-root-discovery
fix/probe-dispatcher-seam
test/media3engine-mime-tables
test/mediaprobe-pure-helpers
fix/codec-vocabulary-drift
docs/robolectric-rationale-correction
docs/api37-advisory-counts
test/r38-8-saf-e2e
test/r38-7-join-states
test/r38-6-conversion-states
test/r38-5-state-seam
fix/jacoco-robolectric-coverage
docs/instrumented-tests-correction
test/r38-2-filecard
test/r38-4-advanced-picker
test/r38-3-pickers
tools/file-issue-script
tools/api-37-emulator
fix/review-app-gaps
docs/review-corrections
No results found.
Labels
Clear labels
above-cut
accessibility
backlog
bug
confirmed
documentation
duplicate
enhancement
good first issue
help wanted
invalid
plausible
question
sev:high
sev:low
sev:medium
wontfix
Worked autonomously overnight: local, JVM-verifiable, no product decision
Barrier affecting people with disabilities
Held for manual review: product/UX call, CI/workflow, hardware, or unverifiable here
Something isn't working
Reviewer demonstrated the defect
Improvements or additions to documentation
This issue or pull request already exists
New feature or request
Good for newcomers
Extra attention is needed
This doesn't seem right
Reviewer could not fully demonstrate it; treat as unproven
Further information is requested
High severity
Low severity
Medium severity
This will not be worked on
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: JMR-dev/LibreMediaConverter#193
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Wave 4, filed from a coverage read on
main@54ca2dd, 2026-09-02. The shared filter note is on #194.Three sentences a user can be shown, and none of them has ever been produced
All three lines report
ci == 0— never executed. Every existing test throws with a message, so the elvis right side has never been taken anywhere in the suite. AThrowablewith a null message is not exotic:RuntimeException(),IOException()and most platform exceptions raised without an argument all have one.:316has a second line of defence downstream, and it will eat a careless testThis is the part worth reading before writing anything.
ConversionStateMappingTest's "a failure with nothing said still says something" looks like it already covers:316and does not. It drives the read side —map(FAILED, data = Data.EMPTY)— and asserts the same constant that:316writes. And the read side has its own fallback (ConversionViewModel.kt:147-149):So mutating
:316to.orEmpty()writesKEY_ERROR to "", and the ViewModel turns that straight back intoGENERIC_FAILURE_MESSAGE. A test that asserts on the resultingFailedstate stays green under the mutation — the two fallbacks mask each other, which is why the write-side one has survived three waves in the first place.Assert on the worker's own
Result.failureoutputData, not on the state the ViewModel derives from it.RefusedJobTestandForcedFailureTestboth readKEY_ERRORoff the result directly; follow those.The work
Three small tests, each belonging where the surrounding behaviour already lives rather than in a new "null message" class:
:316— a software transcoder that throws a bareRuntimeException(); assertresult.outputData.getString(KEY_ERROR) == GENERIC_FAILURE_MESSAGE.ConversionDependencies.softwareis the seam;ForcedFailureTest's fakes are the model.:631/:416— a publisher that throws a message-less exception frompublish; assert theFailedstate's text isSAVE_FAILED_MESSAGEand thatpendingstill travels on the state, because the retry offer depends on it.FailedSaveRetryTest'sRecordingPublisheris the model, and that file already owns "what each state carries". No downstream fallback exists on this path — these two set_state.valuedirectly — so the state assertion is the right one here.Acceptance: the mutation that must go red
Replace the constant with
.orEmpty()at each site. Restore, confirm green.?: "something else"is not an acceptable mutation: it proves only that the test reads a constant, which is the vacuous shape wave 3 rejected twice.For
:316, confirm the mutation reddens the worker assertion. If it does not, the test is reading the ViewModel and needs moving — see above.