Make sure to run parallel commands part of a composite command in parallel#7075
Conversation
✅ Deploy Preview for odo-docusaurus-preview canceled.
|
|
I can see this error happening in the different platforms, buu I cannot see the relation with the changes made in this PR: |
I was also able to reproduce the same failure locally; not sure either how it is related to the changes here. |
…case of the sub-command names Since this passed the Devfile validation logic, we should use the same logic as in command_composite.go
Okay, I think this is a bit related, because the failing test is using a devfile with a pre-stop event trying to execute a composite command with parallel sub-commands. And with the changes here, we should now be using the actual composite parallel implementation. From the job logs, I noticed the following message: After digging, the sub-commands in the Devfile have an upper case, which seems to be a valid Devfile (even if all command IDs are expected to be lower-case). The composite implementation lowers the case of the sub-commands, while the composite parallel implementation does not. |
|
Kudos, SonarCloud Quality Gate passed!
|








What type of PR is this:
/kind bug
/area devfile-spec
What does this PR do / why we need it:
Which issue(s) this PR fixes:
Fixes #6681
PR acceptance criteria:
Unit test
Integration test
Documentation
How to test changes / Special notes to the reviewer:
See the repro steps in #6681. With the changes in this PR, the output of
odo devshould reflect that the commands are running in parallel: