Skip failing test in TestCommandTests.swift

[MaxDesiatov]

rdar://149936169

This test is currently failing on CI (https://ci.swift.org/job/oss-swift-package-amazon-linux-2-aarch64/4188) and blocks toolchain builds for swift.org.

[MaxDesiatov]

@swift-ci test

[bkhouri]

According to the PR description, this is only failing on Amazon Linux 2, but the test is being disabled for all platform - this is less than ideal.

Can we follow an approach similar to #8546 to disable test only on platforms where tests are failing?

[bkhouri]

Looking at the Jenkins console log, the test output is as follows

Test Case 'TestCommandSwiftBuildTests.testFatalErrorDisplayedCorrectNumberOfTimesWhenSingleXCTestHasFatalErrorInBuildCompilation' started at 2025-04-24 11:01:00.419
/home/build-user/swiftpm/Tests/CommandsTests/TestCommandTests.swift:598: error: TestCommandSwiftBuildTests.testFatalErrorDisplayedCorrectNumberOfTimesWhenSingleXCTestHasFatalErrorInBuildCompilation : XCTAssertEqual failed: ("0") is not equal to ("1") - Actual (0) is not as expected (1)
stdout: ""
stderr: "Building for debugging...\n0%: Constructing description\n\n*** Signal 11: Backtracing from 0xffffbe1bb3cc... done ***\n\n*** Program crashed: Bad pointer dereference at 0x0000000000000021 ***\n\nPlatform: arm64 Linux (Amazon Linux 2)\n\nThread 0 crashed:\n\n  0      0x0000ffffbe1bb3cc _dispatch_event_loop_drain + 1232 in libdispatch.so\n  1 [ra] 0x0000ffffbe1b01fc _dispatch_mgr_invoke + 123 in libdispatch.so\n  2 [ra] 0x0000ffffbe1b0170 _dispatch_mgr_thread + 155 in libdispatch.so\n  3 [ra] 0x0000ffffbe1b356c _dispatch_worker_thread + 455 in libdispatch.so\n  4 [ra] 0x0000ffffbd0a8230 start_thread + 175 in libpthread-2.26.so\n...\n\nThread 1:\n\n  0  null\n...\n\n\nRegisters:\n\n x0 0x0000000000000001  1\n x1 0x0000000000000081  129\n x2 0x0000000000000001  1\n x3 0x0000000000000000  0\n x4 0x0000ffffbe1b0444  09 c0 00 91 3f 08 00 f9 28 7d 5f c8 21 fd 0a c8  ·À··?··ù(}_È!ý·È\n x5 0x0000000000000008  8\n x6 0x0000000000000000  0\n x7 0x0000000000000000  0\n x8 0x0000000000000001  1\n x9 0xfffffffffffffff4  18446744073709551604\nx10 0xfffffffffffffff5  18446744073709551605\nx11 0x0000000000000000  0\nx12 0x001ffe1000000000  9005068950962176\nx13 0x001ffe1000000000  9005068950962176\nx14 0x001ffe9c80000000  9005672393867264\nx15 0xff80004080000000  18410715553715978240\nx16 0x0000000000000001  1\nx17 0x0000ffffbd0b1fa0  fd 7b bd a9 fd 03 00 91 f3 53 01 a9 f4 03 00 aa  ý{½©ý···óS·©ô··ª\nx18 0x0000000000000002  2\nx19 0xffffffffffffffff  18446744073709551615\nx20 0x0000000000000000  0\nx21 0x0000ffffb8f7e488  10 00 00 00 00 00 00 00 f0 0c 00 ac ff ff 00 00  ········ð··¬ÿÿ··\nx22 0x0000000000000000  0\nx23 0x0000000000000002  2\nx24 0x0000ffffbe1f0000  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ················\nx25 0x0000ffffac000cf0  b0 83 01 64 ff ff 00 00 03 00 00 00 00 00 00 00  °··dÿÿ··········\nx26 0x0000ffffbe1f0658  02 00 00 00 00 00 00 01 80 23 00 b4 ff ff 00 00  ·········#·´ÿÿ··\nx27 0x0000000000000010  16\nx28 0x000000007fffffff  2147483647\n fp 0x0000ffffb8f7e610  b0 e6 f7 b8 ff ff 00 00 fc 01 1b be ff ff 00 00  °æ÷¸ÿÿ··ü··¾ÿÿ··\n lr 0x0000ffffbe1bb3bc  e8 03 14 aa 14 fd ff b5 28 0f 40 f9 48 03 00 b4  è··ª·ýÿµ(·@ùH··´\n sp 0x0000ffffb8f7e480  81 c8 55 21 00 00 00 00 10 00 00 00 00 00 00 00  ·ÈU!············\n pc 0x0000ffffbe1bb3cc  09 11 40 f9 14 01 40 f9 e9 03 29 aa 2a 8d 40 b8  ··@ù··@ùé·)ª*·@¸\n\n\nImages (73 omitted):\n\n0x0000ffffbd0a1000–0x0000ffffbd0bc2e0 635e47a0fdc7c1119af7daa8a199ed4e5a738518 libpthread-2.26.so /usr/lib64/libpthread-2.26.so\n0x0000ffffbe17e000–0x0000ffffbe1c81b8 9210e2721747b985f13c846c20f81fe0c4e73001 libdispatch.so     /home/build-user/swift-nightly-install/usr/lib/swift/linux/libdispatch.so\n\nBacktrace took 0.02s\n\n"
Test Case 'TestCommandSwiftBuildTests.testFatalErrorDisplayedCorrectNumberOfTimesWhenSingleXCTestHasFatalErrorInBuildCompilation' failed (2.216 seconds)
Test Suite 'TestCommandSwiftBuildTests' failed at 2025-04-24 11:01:02.635

The test output indicates a failure occurred while build the example Swift Package used in the test, which could mean a regression may have been introduced in the Amazon Linux 2 toolchain build.