[all-commits] [llvm/llvm-project] ffcc00: [lldb][POSIX] Correctly report error copying from ...

David Spickett via All-commits all-commits at lists.llvm.org
Wed Jul 15 03:18:14 PDT 2026


  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: ffcc00a1418e623176f348830ab16ad0ececba72
      https://github.com/llvm/llvm-project/commit/ffcc00a1418e623176f348830ab16ad0ececba72
  Author: David Spickett <david.spickett at arm.com>
  Date:   2026-07-15 (Wed, 15 Jul 2026)

  Changed paths:
    M lldb/source/Plugins/Platform/POSIX/PlatformPOSIX.cpp
    M lldb/test/API/python_api/sbplatform/TestSBPlatform.py

  Log Message:
  -----------
  [lldb][POSIX] Correctly report error copying from remote platform (#207365)

This fixes a bug I found where copying a file from a remote Linux
platform using the API would claim that it succeeded, but it had not.
The local file was read only so it was not updated. The host Linux
platform's copy did not have this bug.

There are two tests, one which will run if the testing platform is not
already a remote. This one spawns a "remote" platform, which is actually
still on the host, but it's enough to take the remote code path in the
POSIX platform implementation.

The second uses the testing platform. If that's a remote, use that, if
it's host then we use the host platform to check local copying
behaviour.

This test is not as specific as I'd like it to be, but I wanted
something that could run on many platforms. Even if the copy fails for a
reason other than permissions, at least we are checking that the failure
is propagated.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications


More information about the All-commits mailing list