- Sort Score
- Result 10 results
- Languages All
Results 41 - 50 of 85 for testOk (0.11 sec)
-
cluster/gce/windows/smoke-test.sh
# fails. # - Move copy-pasted code into reusable functions. # - Continue running all checks after one fails. # - Test service connectivity by running a test pod with an http server and # exposing it as a service (rather than curl-ing from existing system # services that don't serve http requests). # - Add test retries for transient errors, such as:
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Fri May 24 07:02:51 UTC 2024 - 20.6K bytes - Viewed (0) -
subprojects/diagnostics/src/integTest/groovy/org/gradle/api/tasks/diagnostics/DependencyInsightReportVariantDetailsIntegrationTest.groovy
])} ${variantOf('testResultsElementsForTest', [ 'org.gradle.testsuite.name': of('test', ''), 'org.gradle.testsuite.target.name': of('test', ''), 'org.gradle.testsuite.type': of('unit-test', ''), 'org.gradle.verificationtype': of('test-results', ''), 'org.gradle.category': of('verification', 'library'),
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Wed Mar 13 19:52:38 UTC 2024 - 23.3K bytes - Viewed (0) -
.teamcity/performance-tests-ci.json
} } ] }, { "testId" : "org.gradle.performance.regression.android.RealLifeAndroidBuildPerformanceTest.calculate task graph with test finalizer", "groups" : [ { "testProject" : "largeAndroidBuild", "coverage" : { "per_commit" : [ "linux" ] } } ] }, {
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Sat May 11 07:05:12 UTC 2024 - 36.4K bytes - Viewed (0) -
src/cmd/cgo/internal/testsanitizers/cc_test.go
} // hangProneCmd returns an exec.Cmd for a command that is likely to hang. // // If one of these tests hangs, the caller is likely to kill the test process // using SIGINT, which will be sent to all of the processes in the test's group. // Unfortunately, TSAN in particular is prone to dropping signals, so the SIGINT // may terminate the test binary but leave the subprocess running. hangProneCmd
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Fri Feb 09 20:00:56 UTC 2024 - 14.4K bytes - Viewed (0) -
platforms/jvm/java-platform/src/integTest/groovy/org/gradle/integtests/resolve/platforms/JavaPlatformResolveIntegrationTest.groovy
platformModule('') mavenHttpRepo.module("org.test", "platform", "1.9").asGradlePlatform().publish() def moduleA = mavenHttpRepo.module("org.test", "b", "1.9").withModuleMetadata() .withVariant("runtime") { dependsOn("org.test", "platform", "1.9") { attribute(Category.CATEGORY_ATTRIBUTE.name, Category.REGULAR_PLATFORM)
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Thu Oct 05 19:36:14 UTC 2023 - 10.7K bytes - Viewed (0) -
hack/make-rules/test-e2e-node.sh
focus=${FOCUS:-""} skip=${SKIP-"\[Flaky\]|\[Slow\]|\[Serial\]"} # The number of tests that can run in parallel depends on what tests # are running and on the size of the node. Too many, and tests will # fail due to resource contention. 8 is a reasonable default for a # e2-standard-2 node. # Currently, parallelism only affects when REMOTE=true. For local test, # ginkgo default parallelism (cores - 1) is used. parallelism=${PARALLELISM:-8}
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Tue Apr 16 09:46:28 UTC 2024 - 10.7K bytes - Viewed (0) -
testing/performance/src/templates/native-dependents-resources/googleTest/libs/googleTest/1.7.0/include/gtest/gtest-death-test.h
// EXPECT_DEATH_IF_SUPPORTED(statement, regex) and // ASSERT_DEATH_IF_SUPPORTED(statement, regex) expand to real death tests if // death tests are supported; otherwise they just issue a warning. This is // useful when you are combining death test assertions with normal test // assertions in one test. #if GTEST_HAS_DEATH_TEST # define EXPECT_DEATH_IF_SUPPORTED(statement, regex) \ EXPECT_DEATH(statement, regex)
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Thu Apr 04 07:21:38 UTC 2024 - 11.3K bytes - Viewed (0) -
testing/performance/src/templates/native-dependents-resources/googleTest/libs/googleTest/1.7.0/include/gtest/gtest-typed-test.h
// This header implements typed tests and type-parameterized tests. // Typed (aka type-driven) tests repeat the same test for types in a // list. You must know which types you want to test with when writing // typed tests. Here's how you do it: #if 0 // First, define a fixture class template. It should be parameterized // by a type. Remember to derive it from testing::Test. template <typename T>
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Thu Apr 04 07:21:38 UTC 2024 - 10K bytes - Viewed (0) -
platforms/jvm/testing-jvm/src/integTest/groovy/org/gradle/testing/junit/platform/JUnitPlatformEnvironmentIntegrationTest.groovy
expect:
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Sep 18 20:52:40 UTC 2023 - 11.5K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/img/java-test-configurations.png
java-test-configurations.png...
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Nov 27 17:53:42 UTC 2023 - 21.9K bytes - Viewed (0)