-
- Downloads
Migration reports now log their effects. They also do not throw exceptions.
Failing to report a migration is non-fatal, as succesfully written files can still be reported afterwards. synchronousReportEndWithErrors had to be rewritten as instanciating and calling a report would have created a race condition.
Showing
- tapeserver/castor/tape/tapeserver/daemon/DataTransferSession.cpp 2 additions, 2 deletions...ver/castor/tape/tapeserver/daemon/DataTransferSession.cpp
- tapeserver/castor/tape/tapeserver/daemon/MigrationReportPacker.cpp 74 additions, 15 deletions...r/castor/tape/tapeserver/daemon/MigrationReportPacker.cpp
- tapeserver/castor/tape/tapeserver/daemon/MigrationReportPacker.hpp 30 additions, 19 deletions...r/castor/tape/tapeserver/daemon/MigrationReportPacker.hpp
- tapeserver/castor/tape/tapeserver/daemon/MigrationReportPackerTest.cpp 17 additions, 17 deletions...stor/tape/tapeserver/daemon/MigrationReportPackerTest.cpp
- tapeserver/castor/tape/tapeserver/daemon/ReportPackerInterface.hpp 1 addition, 1 deletion...r/castor/tape/tapeserver/daemon/ReportPackerInterface.hpp
- tapeserver/castor/tape/tapeserver/daemon/TapeWriteSingleThread.cpp 12 additions, 12 deletions...r/castor/tape/tapeserver/daemon/TapeWriteSingleThread.cpp
- tapeserver/castor/tape/tapeserver/daemon/TapeWriteTask.cpp 3 additions, 3 deletionstapeserver/castor/tape/tapeserver/daemon/TapeWriteTask.cpp
Loading
Please register or sign in to comment