Issue with Cleanup Causes Pelican Tests to Fail on Subsequent Runs

[Saartank]

When running all tests on the main branch in Pelican, the tests run successfully the first time, however, they fail in subsequent runs. The test that fails specifically is:

TestHandleCLIExecutableAlias/no-alias-mixedCase

It turns out this test copies the pelican executable to a different name PELICAN, but the PELICAN file already exists from the previous run, causing the cp command to fail.

The odd thing about this PELICAN file, which causes the problem, is that it is an empty file. Commands such as ls, find, and file do not detect it, and the rm command says that the file does not exist. However, when rm is run with the -f option, it successfully removes the file, and the test passes after that.

I see that in the test, we do os.Stat(arguments[0]) on line 232 in main_test.go to check if the file already exists. However, just like the bash commands mentioned before, os.Stat also fails to detect the file's presence.