I believe that I'm seeing the same issue, but it's interesting in that the build slave is a Windows machine, while the error message is clearly from our Linux master.
Archiving artifacts [htmlpublisher] Archiving HTML reports... [htmlpublisher] Archiving at BUILD level C:\Jenkins\dailyBuild\workspace\AMCC-withAllTests\ivyreport.d to /opt/jenkins/jobs/AMCC-withAllTests/builds/408/htmlreports/Ivy_20dependency_20report [htmlpublisher] Archiving at BUILD level C:\Jenkins\dailyBuild\workspace\AMCC-withAllTests\Client\Capture\doc\testng\test-output to /opt/jenkins/jobs/AMCC-withAllTests/builds/408/htmlreports/TestNG_20report ERROR: Directory 'C:\Jenkins\dailyBuild\workspace[REDACTED]\testng\test-output' exists but failed copying to '/opt/jenkins/jobs/[REDACTED]/builds/408/htmlreports/TestNG_20report'. ERROR: This is especially strange since your build otherwise succeeded. Build step 'Publish HTML reports' changed build result to FAILURE
I believe that I'm seeing the same issue, but it's interesting in that the build slave is a Windows machine, while the error message is clearly from our Linux master.
{quote}Archiving artifacts
[htmlpublisher] Archiving HTML reports... [htmlpublisher] Archiving at BUILD level C:\Jenkins\dailyBuild\workspace\AMCC-withAllTests\ivyreport.d to /opt/jenkins/jobs/AMCC-withAllTests/builds/408/htmlreports/Ivy_20dependency_20report [htmlpublisher] Archiving at BUILD level C:\Jenkins\dailyBuild\workspace\AMCC-withAllTests\Client\Capture\doc\testng\test-output to /opt/jenkins/jobs/AMCC-withAllTests/builds/408/htmlreports/TestNG_20report
ERROR: {color:#00875a}*Directory 'C:\Jenkins\dailyBuild\workspace\[REDACTED]\testng\test-output' exists*{color} but {color:#de350b}*failed copying to '/opt/jenkins/jobs/[REDACTED]/builds/408/htmlreports/TestNG_20report'*{color}.
ERROR: This is especially strange since your build otherwise succeeded. Build step 'Publish HTML reports' changed build result to FAILURE
Given the age of this issue, I'm going to close it off to help tidy things up. In the hopefully unlikely event that this is still an issue, please feel free to re-open with some more recent data