m) acquisition of stat to nanosecond string #2294

New issue

Closed

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

kerem commented

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

Owner

📋 Pull Request Information

Original PR: https://github.com/s3fs-fuse/s3fs-fuse/pull/2000
Author: @ggtakec
Created: 7/24/2022
Status: ✅ Merged
Merged: 7/24/2022
Merged by: @gaul

Base: master ← Head: change_stat_in_test

📝 Commits (1)

e8a3a3f Changed the time(a/c/m) acquisition of stat to nanosecond string

📊 Changes

2 files changed (+29 additions, -23 deletions)

View changed files

📝 test/integration-test-main.sh (+17 -17)
📝 test/test-utils.sh (+12 -6)

📄 Description

Relevant Issue (if applicable)

n/a

Details

Current test scripts check the timestamp of files and directories, but this timestamp is unixtime(seconds).
In future tests, there is a possibility of timestamp(atime/ctime/mtime) change within 1 second.
So I changed the stat option to get and compare as a string containing nanoseconds.

I plan to add test cases that require this change later.

_{🔄 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/2000 **Author:** [@ggtakec](https://github.com/ggtakec) **Created:** 7/24/2022 **Status:** ✅ Merged **Merged:** 7/24/2022 **Merged by:** [@gaul](https://github.com/gaul) **Base:** `master` ← **Head:** `change_stat_in_test` --- ### 📝 Commits (1) - [`e8a3a3f`](https://github.com/s3fs-fuse/s3fs-fuse/commit/e8a3a3f7c01784700df9e0777d4a1bc32132a391) Changed the time(a/c/m) acquisition of stat to nanosecond string ### 📊 Changes **2 files changed** (+29 additions, -23 deletions) <details> <summary>View changed files</summary> 📝 `test/integration-test-main.sh` (+17 -17) 📝 `test/test-utils.sh` (+12 -6) </details> ### 📄 Description ### Relevant Issue (if applicable) n/a ### Details Current test scripts check the timestamp of files and directories, but this timestamp is `unixtime`(seconds). In future tests, there is a possibility of timestamp(`atime`/`ctime`/`mtime`) change within 1 second. So I changed the stat option to get and compare as a string containing nanoseconds. _I plan to add test cases that require this change later._ --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>