apiVersion: release-notes/v2
kind: feature
area: traffic-management
issue:
- 39598
releaseNotes:
- |

                message1: {
                    parallel.syncAt(1)
                    parallel.syncAt(2)
                },
                message3: { parallel.syncAt(3) })
        Dispatch<String> target2 = new DispatchStub(
                message2: {
                    parallel.syncAt(2)
                    parallel.syncAt(3)
                })

        when:
        parallel.run {
            dispatch.dispatchTo(target1)

[!fuzz] skip
[short] skip
env GOCACHE=$WORK/cache

# When running seed inputs, T.Parallel should let multiple inputs run in
# parallel.
go test -run=FuzzSeed

# When fuzzing, T.Parallel should be safe to call, but it should have no effect.
# We just check that it doesn't hang, which would be the most obvious
# failure mode.
# TODO(jayconrod): check for the string "after T.Parallel". It's not printed

plugins {
    id('java-library')
}

// tag::parallel-4[]
// tag::parallel-calculated[]
// tag::fork-every[]
// tag::disable-reports[]
tasks.withType(Test).configureEach {
// end::parallel-4[]
// end::parallel-calculated[]
// end::fork-every[]
// end::disable-reports[]

// tag::parallel-4[]
    maxParallelForks = 4
// end::parallel-4[]

// tag::parallel-calculated[]

	"fmt"
	"flag"
)

// This test ensures the order of CONT lines in parallel chatty tests.
func TestChattyParallel(t *testing.T) {
	t.Parallel()

	// The number of concurrent tests running. This is closely tied to the
	// -parallel test flag, so we grab it from the flag rather than setting it
	// to some constant.
	parallel := flag.Lookup("test.parallel").Value.(flag.Getter).Get().(int)

[short] skip

# go test -parallel -1 shouldn't work
! go test -parallel -1 standalone_parallel_sub_test.go
stdout '-parallel can only be given'

# go test -parallel 0 shouldn't work
! go test -parallel 0 standalone_parallel_sub_test.go
stdout '-parallel can only be given'

-- standalone_parallel_sub_test.go --
package standalone_parallel_sub_test

import "testing"

func Test(t *testing.T) {
	ch := make(chan bool, 1)

    private SmokeTestGradleRunner newKotlinRunner(boolean parallel, VersionNumber kotlinVersion, List<String> tasks) {
        List<String> args = []

        // Parallel workers in Kotlin is enabled by Gradle's --parallel flag. See https://youtrack.jetbrains.com/issue/KT-46401/
        // For context on why we test with parallel workers see https://github.com/gradle/gradle/pull/10404
        if (parallel) {
            args = ["--parallel"]
        }

    }

    @Requires(value = IntegTestPreconditions.NotParallelExecutor, reason = """
Don't run in parallel mode, as the expectation for the setup build are incorrect
It could potentially be worth running this in parallel mode to demonstrate the difference between
parallel and configuration cache
""")
    def "runs tasks in same project in parallel by default"() {
        server.start()

        given:
        buildFile << """

	"fmt"
	"flag"
)

// This test ensures the order of CONT lines in parallel chatty tests.
func TestChattyParallel(t *testing.T) {
	t.Parallel()

	// The number of concurrent tests running. This is closely tied to the
	// -parallel test flag, so we grab it from the flag rather than setting it
	// to some constant.
	parallel := flag.Lookup("test.parallel").Value.(flag.Getter).Get().(int)

import (
	"testing"

	"issue.56370/filter"
)

func Test1(t *testing.T) {
	t.Parallel()

	_ = filter.New()
}

func Test2(t *testing.T) {
	t.Parallel()

	_ = filter.New()
}

func Test3(t *testing.T) {
	t.Parallel()

	_ = filter.New()
}

func Test4(t *testing.T) {
	t.Parallel()

	_ = filter.New()