[PR #1232] [MERGED] Not trap chown command errors directly #1876

New issue

Closed

opened 2026-03-04 02:02:36 +03:00 by kerem · 0 comments

kerem commented

2026-03-04 02:02:36 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/s3fs-fuse/s3fs-fuse/pull/1232
Author: @ggtakec
Created: 1/28/2020
Status: ✅ Merged
Merged: 1/28/2020
Merged by: @ggtakec

Base: master ← Head: test_err_avoid

📝 Commits (1)

010a6b8 Not trap chown command errors directly

📊 Changes

1 file changed (+8 additions, -1 deletions)

View changed files

📝 test/integration-test-main.sh (+8 -1)

📄 Description

Relevant Issue (if applicable)

n/a

Details

If the test_chown() of the test script causes an error (mainly related to file permission) for the chown command, the script is trapped at that point.
This seems to occur when the ensure_diskfree option is specified in Travis CI of MacOS.
Even if the chown command error is not trapped directly, it can be detected as an error in the immediately following judgment statement.
Therefore, it is patched to avoid trapping chown command errors directly.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/s3fs-fuse/s3fs-fuse/pull/1232 **Author:** [@ggtakec](https://github.com/ggtakec) **Created:** 1/28/2020 **Status:** ✅ Merged **Merged:** 1/28/2020 **Merged by:** [@ggtakec](https://github.com/ggtakec) **Base:** `master` ← **Head:** `test_err_avoid` --- ### 📝 Commits (1) - [`010a6b8`](https://github.com/s3fs-fuse/s3fs-fuse/commit/010a6b83efdc503a5f3c5e7ea9d5af51af0b893e) Not trap chown command errors directly ### 📊 Changes **1 file changed** (+8 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `test/integration-test-main.sh` (+8 -1) </details> ### 📄 Description ### Relevant Issue (if applicable) n/a ### Details If the test_chown() of the test script causes an error (mainly related to file permission) for the chown command, the script is trapped at that point. This seems to occur when the ensure_diskfree option is specified in Travis CI of MacOS. Even if the chown command error is not trapped directly, it can be detected as an error in the immediately following judgment statement. Therefore, it is patched to avoid trapping chown command errors directly. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>