WPORG deploy long runtime and failure

[jeffpaul]

Description

In the v0.1.1 release process, the WPORG deploy action took 13m 32s to get through the WordPress Plugin Deploy step and failed with messages of:

svn: E000002: Commit failed (details follow):
svn: E000002: Can't open file '/home/svn/repos/wp-plugins/db/transactions/3407599-242oz.txn/props': No such file or directory
Error: Process completed with exit code 1.

The Upload release asset step was then skipped as was the Post Use desired version of Node.js step.

Step-by-step reproduction instructions

View: https://github.com/WordPress/ai/actions/runs/19850756043/job/56876881049.

Screenshots, screen recording, code snippet

logs_51216308732.zip

Environment info

No response

Please confirm that you have searched existing issues in the repo.

• Yes

Please confirm that you have tested with all plugins deactivated except AI Experiments plugin.

• Yes

Please confirm which theme type you used for testing.

• Block
• Classic
• Hybrid (e.g. classic with theme.json)
• Not sure

[dkotter]

Looking at the logs for that run, it seems like it did successfully deploy all files to the SVN repo, is that correct? Or did you have to manually upload files after the fact?

In searching that error message, it seems it's an error that comes from the remote side (in this case the SVN repo on .org) and not an issue on our end. One scenario I saw that seems a close match to our situation is when a commit takes a long time and the filesystem on the remote server is setup in a certain way, this .txn file can be locked and cause the error message we're seeing.

Because this was our initial deploy and we had lots of files to commit (due to all of our dependencies we pull in via composer) that process took a long time. I'm hopeful that going forward things will be much faster (as we'll have less files to commit) and we won't encounter this issue, though hard to know for sure until the next release.

[jeffpaul]

Yeah I was hoping the run time was due to the first push of files, and I did test the resulting zip on WPORG and things worked as expected. So perhaps all is well and we can close this but keep an eye on the next release (which BTW I might do later tonight with the readme update and the couple small copy tweak issues I opened last night).