- Sort Score
- Result 10 results
- Languages All
Results 21 - 30 of 58 for correctness (0.22 sec)
-
platforms/documentation/docs/src/docs/userguide/authoring-builds/other/test_kit.adoc
A contrived build can be created (e.g. programmatically, or from a template) that exercises the “logic under test”. The build can then be executed, potentially in a variety of ways (e.g. different combinations of tasks and arguments). The correctness of the logic can then be verified by asserting the following, potentially in combination: * The build's output; * The build's logging (i.e. console output);
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Tue Apr 23 05:36:09 UTC 2024 - 15.8K bytes - Viewed (0) -
staging/src/k8s.io/apimachinery/pkg/runtime/serializer/cbor/cbor_test.go
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ // The tests in this package focus on the correctness of its implementation of // runtime.Serializer. The specific behavior of marshaling Go values to CBOR bytes and back is // tested in the ./internal/modes package, which is used both by the Serializer implementation and
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Mon May 13 14:57:12 UTC 2024 - 20.1K bytes - Viewed (0) -
pilot/pkg/serviceregistry/kube/controller/endpointslice.go
// this may happen due to eventually consistency issues, out of order events, etc. In this case, the caller // should not precede with the endpoint, or inaccurate information would be sent which may have impacts on // correctness and security. // // Note: this is only used by endpointslice controller func getPod(c *Controller, ip string, ep *metav1.ObjectMeta, targetRef *corev1.ObjectReference, host host.Name) (*corev1.Pod, bool) {
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Thu May 23 21:07:03 UTC 2024 - 16.9K bytes - Viewed (0) -
platforms/core-execution/execution/src/integTest/groovy/org/gradle/internal/execution/IncrementalExecutionIntegrationTest.groovy
then: result.execution.get().outcome == EXECUTED_NON_INCREMENTALLY !result.reusedOutputOriginMetadata.present result.executionReasons == ["Incremental execution has been disabled to ensure correctness. Please consult deprecation warnings for more details."] } def "out of date when output file removed"() { given: execute(unitOfWork) when: outputFile.delete()
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Fri Mar 08 10:36:34 UTC 2024 - 23.7K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/authoring-builds/plugins/testing_gradle_plugins.adoc
---- [[functional-tests]] === Implementing functional tests Functional tests verify the correctness of the plugin end-to-end. In practice, this means applying, configuring, and executing the functionality of the plugin implementation.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Mar 18 22:49:20 UTC 2024 - 16K bytes - Viewed (0) -
src/runtime/HACKING.md
Usually you want `go:nowritebarrierrec`. `go:nowritebarrier` is primarily useful in situations where it's "nice" not to have write barriers, but not required for correctness. go:nowritebarrierrec and go:yeswritebarrierrec ---------------------------------------------- `go:nowritebarrierrec` directs the compiler to emit an error if the
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Mon Mar 25 19:53:03 UTC 2024 - 13.9K bytes - Viewed (0) -
platforms/core-configuration/configuration-cache/src/main/kotlin/org/gradle/internal/cc/impl/fingerprint/ConfigurationCacheFingerprintWriter.kt
} // TODO(https://github.com/gradle/gradle/issues/22494) ValueSources become part of the fingerprint even if they are only obtained // inside other value sources. This is not really necessary for the correctness and causes excessive cache invalidation. when (val parameters = obtainedValue.valueSourceParameters) { is FileContentValueSource.Parameters -> { parameters.file.orNull?.asFile?.let { file ->
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Sat Jun 08 11:29:30 UTC 2024 - 32.8K bytes - Viewed (0) -
subprojects/core/src/integTest/groovy/org/gradle/api/tasks/CachedCustomTaskExecutionIntegrationTest.groovy
} when: withBuildCache().run "invalid", "--info" then: outputContains("""|Caching disabled for task ':invalid' because: | Caching has been disabled to ensure correctness. Please consult deprecation warnings for more details. """.stripMargin()) executedAndNotSkipped(":invalid") } private static String defineCachedTask(String suffix = "") { """
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon May 20 11:16:24 UTC 2024 - 30.6K bytes - Viewed (0) -
pilot/pkg/xds/ads.go
request := &model.PushRequest{ Full: true, Push: con.proxy.LastPushContext, Reason: model.NewReasonStats(model.ProxyRequest), // The usage of LastPushTime (rather than time.Now()), is critical here for correctness; This time // is used by the XDS cache to determine if a entry is stale. If we use Now() with an old push context, // we may end up overriding active cache entries with stale ones. Start: con.proxy.LastPushTime,
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Mon Jun 03 08:29:05 UTC 2024 - 23.4K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/releases/upgrading/upgrading_version_6.adoc
Sometimes, Ant's default excludes prove problematic, for example when you want to include the `.gitignore` in an archive file. Changing Gradle's default excludes during the execution phase can lead to correctness problems with up-to-date checks. As a consequence, you are only allowed to change Gradle's default excludes in the settings script, see the <<working_with_files.adoc#sec:change_default_excludes,user manual>> for an example.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Apr 01 15:00:23 UTC 2024 - 44.8K bytes - Viewed (0)