Repository navigation
docs(tasks): file CI's rocfl check failing on a valid object - #3
Merged
adammharris merged 1 commit intoOct 27, 2026
Merged
Conversation
rocfl validates the interop directory as a storage root, reports the missing root declaration, and exits 2. The job's shell stops there under -e and pipefail, before the grep that was meant to tolerate it, so `rocfl cross-validation` fails on main although rocfl finds the object valid. Validating with `--paths interop-object` checks the object alone.
adammharris
deleted the
agent/backlog-rocfl-check-fails-on-a-valid-object
branch
October 30, 2026 01:26
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds the task
docs/tasks/rocfl-check-fails-on-a-valid-object.mdand lists it in the tasks index. Docs only: no code or workflow changes.Why
The
rocfl cross-validationjob has failed on every push tomain. Before the move to fig 7 it stopped inEmit an object. Now it gets as far asValidate it with rocfland fails there (run 40249398822, on e9960ea).rocfl 1.7.0 validates the directory as a storage root, reports
E069 Root version declaration does not exist, and exits 2, even though it also reportsInvalid objects: 0. The step runs with-eandpipefail, so it stops before thegrepthat was supposed to tolerate the missing root.--suppress-error E069still exits 2.rocfl validate --paths interop-objectchecks the object on its own.The task records the repro and a done state. It does not choose the fix.
How it was found and checked
On hbox, from e9960ea, with rocfl 1.7.0 installed into a scratch directory:
rocfl -r <out> validateexits 2 withInvalid objects: 0, the same as CI.rocfl -r <out> validate --paths interop-objectexits 0.prov checkshows only theabout.mdfinding, whichmainalready has.