Fix for flaky test by updating filetype from .txt to no extension

[snehara99]

The problem was that on Windows, the .txt extension triggers file associations (e.g., .txt → Notepad), causing Windows to launch Notepad instead of failing with BAD_COMMAND. That's why the test hung for 763 seconds before being killed with a SEGFAULT.

The correct fix is:

• Rename notAnExe.txt to notAnExe (no extension) to avoid Windows file associations
• Add a TIMEOUT 30 property as a safety net
• Update references accordingly

[snehara99]

The problem was that on Windows, the .txt extension triggers file associations (e.g., .txt → Notepad), causing Windows to launch Notepad instead of failing with BAD_COMMAND. That's why the test hung for 763 seconds before being killed with a SEGFAULT.

The correct fix is:

• Rename notAnExe.txt to notAnExe (no extension) to avoid Windows file associations
• Add a TIMEOUT 30 property as a safety net
• Update references accordingly

[snehara99]

The problem was that on Windows, the .txt extension triggers file associations (e.g., .txt → Notepad), causing Windows to launch Notepad instead of failing with BAD_COMMAND. That's why the test hung for 763 seconds before being killed with a SEGFAULT.

The correct fix is:

• Rename notAnExe.txt to notAnExe (no extension) to avoid Windows file associations
• Add a TIMEOUT 30 property as a safety net
• Update references accordingly

[snehara99]

The problem was that on Windows, the .txt extension triggers file associations (e.g., .txt → Notepad), causing Windows to launch Notepad instead of failing with BAD_COMMAND. That's why the test hung for 763 seconds before being killed with a SEGFAULT.

The correct fix is:

• Rename notAnExe.txt to notAnExe (no extension) to avoid Windows file associations
• Add a TIMEOUT 30 property as a safety net
• Update references accordingly

[snehara99]

The problem was that on Windows, the .txt extension triggers file associations (e.g., .txt → Notepad), causing Windows to launch Notepad instead of failing with BAD_COMMAND. That's why the test hung for 763 seconds before being killed with a SEGFAULT.

The correct fix is:

• Rename notAnExe.txt to notAnExe (no extension) to avoid Windows file associations
• Add a TIMEOUT 30 property as a safety net
• Update references accordingly

[snehara99]

The problem was that on Windows, the .txt extension triggers file associations (e.g., .txt → Notepad), causing Windows to launch Notepad instead of failing with BAD_COMMAND. That's why the test hung for 763 seconds before being killed with a SEGFAULT.

The correct fix is:

• Rename notAnExe.txt to notAnExe (no extension) to avoid Windows file associations
• Add a TIMEOUT 30 property as a safety net
• Update references accordingly

[snehara99]

The problem was that on Windows, the .txt extension triggers file associations (e.g., .txt → Notepad), causing Windows to launch Notepad instead of failing with BAD_COMMAND. That's why the test hung for 763 seconds before being killed with a SEGFAULT.

The correct fix is:

• Rename notAnExe.txt to notAnExe (no extension) to avoid Windows file associations
• Add a TIMEOUT 30 property as a safety net
• Update references accordingly

[snehara99]

The problem was that on Windows, the .txt extension triggers file associations (e.g., .txt → Notepad), causing Windows to launch Notepad instead of failing with BAD_COMMAND. That's why the test hung for 763 seconds before being killed with a SEGFAULT.

The correct fix is:

• Rename notAnExe.txt to notAnExe (no extension) to avoid Windows file associations
• Add a TIMEOUT 30 property as a safety net
• Update references accordingly