test: use multi-issuer file registration rings#25
Merged
Conversation
Signed-off-by: Robin He <git@hybscloud.com>
There was a problem hiding this comment.
Pull request overview
This PR reduces CI sensitivity in file-registration integration tests by opting into multi-issuer ring setup, and updates the agent guide wording/notation to describe work “around the boundary” more precisely.
Changes:
- Enable
Options.MultiIssuersin file-registration integration tests to avoidSINGLE_ISSUERregister-time task-affinity failures in CI. - Reword the READMEs (and
AGENTS.md) from “above or beyond” to “around the boundary”. - Split completion vs submission instance cases in
agents/formalization/notation.md.
Reviewed changes
Copilot reviewed 8 out of 8 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| README.md | Rewords the agentic-coding section to “around the code.hybscloud.com/uring boundary”. |
| README.zh-CN.md | Same wording update in Simplified Chinese. |
| README.ja.md | Same wording update in Japanese. |
| README.fr.md | Same wording update in French. |
| README.es.md | Same wording update in Spanish. |
| AGENTS.md | Updates entrypoint wording to “around the package boundary” and tightens the navigation paragraph. |
| agents/formalization/notation.md | Adds explicit completion/submission instance case sets and updates the invariant accordingly. |
| integration_linux_test.go | Sets MultiIssuers = true in file-registration integration tests to avoid CI affinity failures. |
Comment on lines
+50
to
+52
| ## Codage agentique autour de la frontière `code.hybscloud.com/uring` | ||
|
|
||
| Utilisez le point d'entrée du guide autonome [`AGENTS.md`](./AGENTS.md) lorsque vous générez ou relisez du code appelant au-dessus ou au-delà de `code.hybscloud.com/uring`. Utilisez [`agents/INDEX.md`](./agents/INDEX.md) comme index thématique afin de préserver la frontière noyau : mécanique SQE/CQE, identité `user_data`, propriété des tampons, résultats de complétion, règles de cycle de vie, limites d'intégration, contrôles de référence et le flux depuis l'analyse et la formalisation jusqu'au raisonnement, à la compilation vers Go et à la vérification. | ||
| Utilisez le point d'entrée du guide autonome [`AGENTS.md`](./AGENTS.md) lorsque vous générez ou relisez du code appelant autour de la frontière `code.hybscloud.com/uring` : runtimes, piles de protocoles, services et travaux de revue qui exigent une frontière Linux `io_uring` précise. Utilisez [`agents/INDEX.md`](./agents/INDEX.md) comme index thématique afin de préserver la frontière noyau : mécanique SQE/CQE, identité `user_data`, propriété des tampons, résultats de complétion, règles de cycle de vie, limites d'intégration, contrôles de référence et le flux depuis l'analyse et la formalisation jusqu'au raisonnement, à la compilation vers Go et à la vérification. |
Comment on lines
+50
to
+52
| ## Codificación orientada a agentes alrededor de la frontera `code.hybscloud.com/uring` | ||
|
|
||
| Utilice el punto de entrada de la guía independiente [`AGENTS.md`](./AGENTS.md) al generar o revisar código del llamador sobre o más allá de `code.hybscloud.com/uring`. Use [`agents/INDEX.md`](./agents/INDEX.md) como índice de temas para conservar la frontera del núcleo: mecánica SQE/CQE, identidad en `user_data`, propiedad de búferes, resultados de finalización, reglas de ciclo de vida, límites de integración, comprobaciones de referencia y el flujo desde análisis y formalización hasta razonamiento, compilación a Go y verificación. | ||
| Utilice el punto de entrada de la guía independiente [`AGENTS.md`](./AGENTS.md) al generar o revisar código del llamador alrededor de la frontera `code.hybscloud.com/uring`: runtimes, pilas de protocolos, servicios y trabajos de revisión que necesitan una frontera Linux `io_uring` precisa. Use [`agents/INDEX.md`](./agents/INDEX.md) como índice de temas para conservar la frontera del núcleo: mecánica SQE/CQE, identidad en `user_data`, propiedad de búferes, resultados de finalización, reglas de ciclo de vida, límites de integración, comprobaciones de referencia y el flujo desde análisis y formalización hasta razonamiento, compilación a Go y verificación. |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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
This PR removed CI-sensitive single-issuer affinity from file-registration integration tests.
Changes
MultiIssuersin file-registration integration tests to avoidSINGLE_ISSUERregistration task-affinity failures in CI.agents/formalization/notation.md.