When user is setting a runtime argument as preference, the default compute profile is also saved. This compute profile should not be set unless the user have explicitly change the compute profile
Steps to reproduce problem:
- Create a pipeline with macro
- Add the runtime argument and click save
- Run the pipeline
- Create a new compute profile and set that profile as default
- The old default is still set as the default of the pipeline instead of the new default.