exceptionfactory commented on PR #8152:
URL: https://github.com/apache/nifi/pull/8152#issuecomment-1907356923

   > > Thanks for making the updates @simonbence.
   > > On closer review of the test changes, there is still a problem with 
manager tests not cleaning up temporary files on completion. Disabling the 
methods on Windows masks this problem, but running the tests on macOS shows 
`junit` directories left behind after completion. I recommend removing the 
`DisabledOnOS` annotations and tracking down the source of the problem. Whether 
in the test class, or the implementation itself, temporary files should not 
remain after successful test completion.
   > > I also noticed several QuestDB table definitions that still use 
`capturedAt` as the column name, so this should be checked across the set of 
changes and updated.
   > 
   > I take a look on the leftover temporary files.
   > 
   > As for disable: It was a deliberate choice after looking into the reasons. 
I picked adding them due to the test setup, not because of production reasons. 
In order to emulate corrupted database files I directly touch the files and 
write some gibberish into that. This is something normally would happened 
outside of our code, most reasonably would happen within the database. I did 
not found other way to trigger this however Windows does not let one to touch a 
file is under lock by an other process. If there is an other way to deliberatly 
corrupt the database (not directly working with the underlying files) than it 
could work out, but I am not aware of such a method.
   
   Thanks for looking into the details. Manual file changes for the test 
methods seems like a reasonable strategy, so if you can track down and resolve 
the leftover files issue, I would expect that should also resolve the test 
failures on Windows.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to