This is a Salesforce BUG
Update: November 17, 2020
A fix has been submitted for this issue. Enablement of the fix requires you to contact Salesforce Support and ask that the fix be applied to your Organization that is encountering the issue.
There is an issue with the transaction management on the changeset deployment for Lightning Web Components and Aura components containing Lightning Message Channel.
The above types of components cannot be deployed using changesets presently due to the fatal error below:
"Fatal Error Programmer error: Cannot compare savepoints from two different transactions Field info: entity name = LightningComponentResource, field name = Source"
Users will notice an unusual behavior during validation/deployment on the UI, where it looks like it's reverting back after completion and re-trying before it fails with the above error. This operation can take a long time even with a small number of components being deployed.
Message Channel, on its own, can be deployed through changesets
Another symptom is Managed-package Patch orgs showing as "Creating" indefinitely.
- Deploy a Message Channel into the org using any deployment method
- Create an inbound changeset with either LWC or Aura referencing the message channel and upload to target org
- In the target org, validate or deploy the above changeset from inbound changesets
- Notice the unusual behavior during validation/deployment and see the fatal error.
Use any deployment method aside from changesets to deploy components containing Lightning Message Channel.