Repository navigation
[DO NOT MERGE] CI proof 2: one production file left out of the inventory (L3 must turn red) - #178
Closed
sinkog wants to merge 1 commit into
Conversation
…tory (proof that the L3 completeness check turns the job red) --- [signing-metadata] key = cic-my-sign-key signature = vault:v1:MEUCIAiZtDr0XjL/wb8UaQukfCtsdDNCXzPerKIVs/oznHgFAiEAnKSLMH3XmhNQcmnx55zCJn7WMBDxXQx0R2F93PWOYFY= hash-algorithm = sha256 digest = /f2tVHDeGezceQQiUaEsIuS6e+foatnGK1HrHLVB15I= [certificate] -----BEGIN CERTIFICATE----- MIICBjCCAaygAwIBAgIUSnRMR6RPnEbg296XWPOqq/u5PCwwCgYIKoZIzj0EAwIw QzELMAkGA1UEBhMCSFUxGTAXBgNVBAoMEENlbnRyYWxJbmZyYUNvcmUxGTAXBgNV BAMMEENJQyBEZXZlbG9wZXIgQ0EwHhcNMjYwMzIwMTMyMjU5WhcNMjYxMjMxMTMy MjU5WjBFMQswCQYDVQQGEwJIVTEZMBcGA1UECgwQQ2VudHJhbEluZnJhQ29yZTEb MBkGA1UEAwwSR2Fib3IgWm9sdGFuIFNpbmtvMFkwEwYHKoZIzj0CAQYIKoZIzj0D AQcDQgAEIG2CVmTfmLB9pLLclj7YmP2eedAjklpy4LGrU2ijoiy6Xqpuybv7OgJe i+ez31s65NEV8+X/ByeX1cstR988z6N8MHowCQYDVR0TBAIwADAdBgNVHQ4EFgQU yZN6AIX/TNnIJ9GwAa/NRN3ujHAwHwYDVR0jBBgwFoAUXn6CHYzPUqU4JVP8g+OS WeDYjhcwDgYDVR0PAQH/BAQDAgeAMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEF BQcDBDAKBggqhkjOPQQDAgNIADBFAiEA+bFzXRoJ4PCQbhAAtpkcMjt0vNj5rEW0 lOMBGDNyaWkCIB1vmM7PcZzv/c9bIrxF5kqv6QXomouhByUfeNUTbpKW -----END CERTIFICATE-----
Member
Author
|
Closed, not merged: the proof is complete. object-evidence run 43639959355, head 514d9e4: L1 INTEGRITY_OK, L2 BOUND_TO_INPUTS, L3 FAIL (461 objects but 464 top-level func lines). Recorded in the PR-04 report. |
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.
DO NOT MERGE. This PR exists only to show, in a real GitHub Actions run, that the L3 completeness check of the object-evidence verifier turns the job red.
It is the clean successor of the draft #175: based on the fixed PR-04 work branch (#174, head 34043f7, which removed the fixture package that broke
coverageand the mutation gate on the first run), and it changes one line ofobject-evidence.yml: the last production file is left out of the Go inventory (head -n -1). The object list is then incomplete against the independentfunc-line count of the scope, soobject_model.py verifymust reportL3 FAILand theobject-evidencejob must fail. L1 and L2 stay green.Expected:
object-evidencered withgo unit 'root': … objects but … top-level func lines in the source. The run id is recorded in the PR-04 report (cic-factoryjobs/relay-ci-parity-04-object-level-measurement/output/pr04-report.md). This PR is closed after the run.