Skip to content

[lldb][Windows] Fixed the test TestGdbRemoteMemoryTagging #92077

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

slydiman
Copy link
Contributor

Windows path is case insensitive. Tests test_QMemTags_packets and test_qMemTags_packets will use the same build dir and conflict. Added a suffix to resolve conflicts.

Windows path is case insensitive. Tests `test_QMemTags_packets` and `test_qMemTags_packets` will use the same build dir and conflict. Added a suffix to resolve conflicts.
@slydiman slydiman requested a review from JDevlieghere as a code owner May 14, 2024 07:52
@llvmbot llvmbot added the lldb label May 14, 2024
@llvmbot
Copy link
Member

llvmbot commented May 14, 2024

@llvm/pr-subscribers-lldb

Author: Dmitry Vasilyev (slydiman)

Changes

Windows path is case insensitive. Tests test_QMemTags_packets and test_qMemTags_packets will use the same build dir and conflict. Added a suffix to resolve conflicts.


Full diff: https://github.com/llvm/llvm-project/pull/92077.diff

1 Files Affected:

  • (modified) lldb/test/API/tools/lldb-server/memory-tagging/TestGdbRemoteMemoryTagging.py (+2-2)
diff --git a/lldb/test/API/tools/lldb-server/memory-tagging/TestGdbRemoteMemoryTagging.py b/lldb/test/API/tools/lldb-server/memory-tagging/TestGdbRemoteMemoryTagging.py
index 584de5e2ef49e..e14c7b4a39d58 100644
--- a/lldb/test/API/tools/lldb-server/memory-tagging/TestGdbRemoteMemoryTagging.py
+++ b/lldb/test/API/tools/lldb-server/memory-tagging/TestGdbRemoteMemoryTagging.py
@@ -84,7 +84,7 @@ def prep_memtags_test(self):
     @skipUnlessArch("aarch64")
     @skipUnlessPlatform(["linux"])
     @skipUnlessAArch64MTELinuxCompiler
-    def test_qMemTags_packets(self):
+    def test_qMemTags_packets_A(self):
         """Test that qMemTags packets are parsed correctly and/or rejected."""
         buf_address, page_size = self.prep_memtags_test()
 
@@ -154,7 +154,7 @@ def check_tag_write(self, body, expected):
     @skipUnlessArch("aarch64")
     @skipUnlessPlatform(["linux"])
     @skipUnlessAArch64MTELinuxCompiler
-    def test_QMemTags_packets(self):
+    def test_QMemTags_packets_B(self):
         """Test that QMemTags packets are parsed correctly and/or rejected."""
         buf_address, page_size = self.prep_memtags_test()
 

@slydiman slydiman requested review from DavidSpickett and labath May 14, 2024 07:53
@@ -84,7 +84,7 @@ def prep_memtags_test(self):
@skipUnlessArch("aarch64")
@skipUnlessPlatform(["linux"])
@skipUnlessAArch64MTELinuxCompiler
def test_qMemTags_packets(self):
def test_qMemTags_packets_A(self):
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've seen this with a packet test before, the GDB protocol likes to use first character lower case for read and upper case for write.

https://sourceware.org/gdb/current/onlinedocs/gdb.html/General-Query-Packets.html

So yes let's change the name but how about this instead:

test_tag_read_qMemTags_packets
test_tag_write_QMemTags_packets

Then it's clearer why there are 2 tests.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

@slydiman slydiman requested a review from DavidSpickett May 14, 2024 08:37
@DavidSpickett DavidSpickett merged commit 429ce59 into llvm:main May 14, 2024
4 checks passed
@slydiman slydiman deleted the fix-lldb-test-TestGdbRemoteMemoryTagging branch July 25, 2024 21:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants