Search Options

Display Count
Sort
Preferred Language
Advanced Search

Results 1 - 3 of 3 for Scenarios (0.05 seconds)

  1. docs/en/docs/release-notes.md

    **Note**: You probably don't need `contextvars`, and you should probably avoid using them. But they are powerful and useful in some advanced scenarios, for example, migrating from code that used Flask's `g` semi-global variable.
    
    Created: Sun Apr 05 07:19:11 GMT 2026
    - Last Modified: Fri Apr 03 12:07:04 GMT 2026
    - 631K bytes
    - Click Count (0)
  2. .teamcity/src/main/kotlin/projects/StageProject.kt

                            "on ${os.asName()} (bucket $bucketIndex)",
                    performanceSubProject = "performance",
                    bucketIndex = bucketIndex,
                    extraParameters =
                        "--profiler $profiler --tests \"${performanceScenario.scenario.className}.${performanceScenario.scenario.scenario}\"",
    Created: Wed Apr 01 11:36:16 GMT 2026
    - Last Modified: Mon Mar 30 04:44:29 GMT 2026
    - 12.5K bytes
    - Click Count (0)
  3. .teamcity/src/main/kotlin/util/AdHocPerformanceScenario.kt

    abstract class AdHocPerformanceScenario(
        os: Os,
        arch: Arch = Arch.AMD64,
    ) : BuildType({
            val id = "Util_Performance_AdHocPerformanceScenario${os.asName()}${arch.asName()}"
            name = "AdHoc Performance Scenario - ${os.asName()} ${arch.asName()}"
            id(id)
    
            applyPerformanceTestSettings(os = os, arch = arch, timeout = 420)
            setArtifactRules(INDIVIDUAL_PERFORAMCE_TEST_ARTIFACT_RULES)
    
            params {
    Created: Wed Apr 01 11:36:16 GMT 2026
    - Last Modified: Mon Mar 30 14:08:32 GMT 2026
    - 6K bytes
    - Click Count (0)
Back to Top