You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Strange one... A colleague ran a test on a device and is encountering the below when attempting to download the report file(s).
Corresponding line in Testrun output.
See below ls -l.
I did wonder whether case sensitivity/similarity of device names thus directory names may be a contributor somewhere along the line? The testrun process was started as ossadmin using sudo testrun and has been running for a number of days with other reports accessible without issue.
Interestingly, even after suitable chown -R of the affected reports directory...
...the report(s) are still unavailable for download.
Error logs
This is the reports directory, containing 2 tests. The first one (that colleague was trying to initially download above), and a second one that should contain more useful info in the testrun.log file.
For the avoidance of doubt in case the similarity in directory names is a cause of concern, the two devices/directories do relate to two completely separate physical Tridium JACE 8000's with 2 entirely different configurations/ports open/etc.
Describe the bug
Strange one... A colleague ran a test on a device and is encountering the below when attempting to download the report file(s).
Corresponding line in Testrun output.
See below
ls -l
.I did wonder whether case sensitivity/similarity of device names thus directory names may be a contributor somewhere along the line? The testrun process was started as ossadmin using
sudo testrun
and has been running for a number of days with other reports accessible without issue.Interestingly, even after suitable
chown -R
of the affected reports directory......the report(s) are still unavailable for download.
Error logs
This is the
reports
directory, containing 2 tests. The first one (that colleague was trying to initially download above), and a second one that should contain more useful info in thetestrun.log
file.reports.zip
Environment (please provide the following information about your setup):
Additional context
Only modifications from official 2.1 release are as below.
The text was updated successfully, but these errors were encountered: