ci: classify CloudStorage root permission failures (TIN-1547) - #400
Merged
Conversation
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.
Summary
cloudstorage_root_permission_deniedfailure-classification-input.log, includingcloud-root-find.errand FileProvider system diagnosticsrebuild_domaindispatch input formacos-postinstall-smoke.yml, wiring it to the existing--rebuild-domainhost-app remove/re-add pathEvidence
bash scripts/test-macos-postinstall-smoke.shbash scripts/test-release-workflow-fileprovider.shgit diff --checkpython3 -m py_compile scripts/tcfs-smoke-endpoint-preflight.py scripts/test-tcfs-smoke-endpoint-preflight.pyWhy
Post-#399 run 26090322317 no longer misclassified
findstderr as enumeration. It now fails before remote index/requestDownload with persistent CloudStorage root EPERM and fileproviderdfailed to start FPFS for domainevidence. This PR makes that failure first-class and exposes the stale-domain rebuild lever for the next rerun.Claim boundary
This still does not prove production FileProvider hydration. It improves failure classification and provides the next diagnostic/proof path.