Conversation
|
GNU testsuite comparison: |
680b59c to
db64ed6
Compare
|
@xtqqczze could you take a look at it? Thanks! |
With #14586, it would be possible to remove all the |
04fc3ef to
ddb44cc
Compare
| // | ||
| // For the full copyright and license information, please view the LICENSE | ||
| // file that was distributed with this source code. | ||
|
|
There was a problem hiding this comment.
Please rebase to remove the unrelated whitespace changes.
There was a problem hiding this comment.
It's already at the last commit.
|
|
||
| runs-on: ubuntu-latest | ||
| if: > | ||
| github.event.workflow_run.event == 'pull_request' && |
There was a problem hiding this comment.
Sorry, this is a bad merge.
There was a problem hiding this comment.
You will need to cherry-pick from the commit before @sylvestre pushed a merge commit into your branch:
git fetch upstream
git checkout fix/install-strip-text-file-busy
git reset --hard upstream/main
git cherry-pick db64ed6cbe422cc36f2035625fe7774f27094dbdddb44cc to
bb3412a
Compare
Merging this PR will degrade performance by 15.86%
Warning Please fix the performance issues or acknowledge them on CodSpeed. Performance Changes
Tip Investigate this regression by commenting Comparing Footnotes
|
91bfe9b to
39df9cf
Compare
39df9cf to
3d9711b
Compare
On Linux, exec(2) of a script (e.g. the #!/bin/sh strip wrapper) transiently fails with ETXTBSY when another process is concurrently exec'ing the same interpreter, because the kernel denies write access to the file for the duration of the exec; CI's parallel test load turns this into an intermittent failure. BSD kernels already sleep and retry on ETXTBSY (see exec(3)), and install now does the same, retrying the strip-program spawn up to three times with a short delay, so genuine errors (missing program, permission, non-zero exit) still fail immediately. Unit tests cover the retry path and confirm only ETXTBSY triggers a retry.
Closes #14520