Lines Matching +full:dependency +full:- +full:check
2 # Use of this source code is governed by a BSD-style license that can be
12 * `Verifier`: A class representing a single verification check.
14 a failed verification check.
38 _HOSTNAME_PATTERN = 'chromeos[0-9]-row[0-9]+[a-z]?-rack[0-9]+[a-z]?-host[0-9]+'
42 # True - verifier run and passed
43 # False - verifier run and failed
44 # None - verifier did not run or dependency failed
69 '_DependencyFailure', ('dependency', 'error', 'tag'))
73 '_NonCriticalDependencyFailure', ('dependency', 'error', 'tag'))
81 failure being passed back from a verification dependency. That is,
83 to signal that the original failure is further down the dependency
88 failed dependency:
89 * The `dependency` attribute of each failure is the description
90 of the failed dependency.
92 the exception from the failed dependency.
119 This writes a short summary of the dependency failures captured
127 dependency in `self` are be logged at DEBUG level. The `deps`
138 logging.debug(' %s', failure.dependency)
141 """Check if the error is considered to be critical to repair process."""
146 " it raised a non-critical error.",
180 @property _dependency_list Dependency pre-requisites.
190 Check if the action is applicable to target host. Subclasses
193 @param host Target host to check.
246 to a failed dependency are omitted.
300 @return A short identifier-like string.
340 Abstract class embodying one verification check.
342 A concrete subclass of `Verifier` provides a simple check that can
344 check found a problem that can cause at least one test to fail.
356 re-running the check code. The `_reverify()` method clears the
361 verification check.
362 * `description`: A one-line summary of the verification check for
376 None - did not run
377 True - successful pass
378 Exception - fail during execution
405 check dependencies, and if they pass, run `verify()`. Log
424 ' check applicability; %s', self.tag, e)
441 message = '(Non-critical)Failed: %s'
457 Unconditionally perform a verification check.
461 * The check should find a problem that will cause testing to
464 and should be optimized for success; a check that passes
470 A verification check should normally trigger a single set of
476 exception text should be a short, 1-line summary of the error.
496 True - verifier passed
497 False - verifier did not pass
498 None - verifier did not run because it is not applicable
499 or blocked due to dependency failure
522 repair action's dependencies fail, the action does not check its
530 * `description`: A one-line summary of the repair action for
540 Re-install the stable build via AU
595 'pre' during pre-repair trigger verification
597 'post' during post-repair trigger verification
650 # If we're blocked by a failed dependency, we exit with an
667 ' during check applicability; %s', self.tag, e)
733 exception text should be a short, 1-line summary of the error.
775 * The `verify()` method walks the verifier DAG in dependency
784 iterable consisting of three-element tuples in the form
794 dependency.
831 argument is an iterable consisting of four-element tuples in the
896 # Metrics - we report on 'actions' for every repair action
1010 True - verifier passed
1011 False - verifier did not pass
1012 None - verifier did not run because it is not applicable
1013 or blocked due to dependency failure
1021 'or blocked due to dependency failure', tag)