tsp-client will delete sparse-spec after copying the spec files to TempTypeSpecFiles. But sparse-spec is a common shared temp directory, when we run tsp-client in parallel, one tsp-client process may delete sparse-spec before other tsp-client finish copying their spec files. As a result the second tsp-client process will fail because of lack of spec files.
Expected:
tsp-client can run in parallel.
Possible solution:
We can create sparse-spec directory for each SDK generation separately, not the use the common one
tsp-clientwill deletesparse-specafter copying the spec files toTempTypeSpecFiles. Butsparse-specis a common shared temp directory, when we runtsp-clientin parallel, onetsp-clientprocess may deletesparse-specbefore othertsp-clientfinish copying their spec files. As a result the secondtsp-clientprocess will fail because of lack of spec files.Expected:
tsp-clientcan run in parallel.Possible solution:
We can create
sparse-specdirectory for each SDK generation separately, not the use the common one