fs: preserve directory timestamps in cp

[abhi128nandan]

fs: preserve directory timestamps in cp

This fixes an issue where fs.cp and fs.cpSync (when a filter is
provided) correctly restore mtime and atime on copied files when
preserveTimestamps: true is passed, but skip restoring them for
directories.

The fix applies the existing setDestTimestamps helper to directories,
ensuring it is called after directory creation/copying but before any
modes are restored (since restoring a read-only mode would prevent
timestamp modification).

Note: This fix covers fs.cp() (async, all cases) and fs.cpSync()
when a filter is provided. The native fast path used by cpSync()
without a filter (CpSyncCopyDir in src/node_file.cc) has the
identical gap and is left for a separate follow-up contribution, since
it requires native code changes and a different review path.

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/76579/

[abhi128nandan]

Could someone please check the result of Jenkins CI job 76579? I’m unable to access the job because Jenkins shows “abhi128nandan is missing the Overall/Read permission”, so I can’t see whether there’s an actual test failure or an infrastructure issue. Thanks!

[sxa]

Could someone please check the result of Jenkins CI job 76579? I’m unable to access the job because Jenkins shows “abhi128nandan is missing the Overall/Read permission”, so I can’t see whether there’s an actual test failure or an infrastructure issue. Thanks!

I woldn't normally see a request like this but I happened to be looking at the job (randomly) for something else so I'll reply. The jobs is still running. The message with the link was only posted 40 minutes ago and it takes longer than that to run through the tests.

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/76600/

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.13%. Comparing base (18eaa73) to head (321146b).
⚠️ Report is 56 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #65540   +/-   ##
=======================================
  Coverage   90.13%   90.13%           
=======================================
  Files         751      751           
  Lines      253656   253644   -12     
  Branches    47787    47800   +13     
=======================================
- Hits       228631   228626    -5     
  Misses      16258    16258           
+ Partials     8767     8760    -7     

Files with missing lines	Coverage Δ
lib/internal/fs/cp/cp-sync.js	70.56% <100.00%> (+7.29%)	⬆️
lib/internal/fs/cp/cp.js	89.02% <100.00%> (+0.16%)	⬆️

... and 32 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[abhi128nandan]

Could a collaborator please approve/re-run the GitHub Actions and start Jenkins CI for the updated HEAD 6661a995? The previous CI run was fully green; I synced the branch with main, which resulted in the new HEAD.

[LiviaMedeiros]

Could a collaborator please approve/re-run the GitHub Actions and start Jenkins CI for the updated HEAD 6661a995? The previous CI run was fully green; I synced the branch with main, which resulted in the new HEAD.

Was there a reason to sync? AFAICT there were no conflicts with current main, it's completely fine to keep PR branch slightly 'outdated' as long as there's no recent changes on main that can't coexist with it.