Hi Jean-Jacques,
On Fri, 8 Feb 2019 at 12:31, Jean-Jacques Hiblot wrote:
>
> + Simon
>
> On 05/02/2019 15:48, Jean-Jacques Hiblot wrote:
> >
> > On 05/02/2019 14:45, Tom Rini wrote:
> >> On Mon, Feb 04, 2019 at 12:19:19PM +0100, Jean-Jacques Hiblot wrote:
> >>> We need to make sure that file
+ Simon
On 05/02/2019 15:48, Jean-Jacques Hiblot wrote:
On 05/02/2019 14:45, Tom Rini wrote:
On Mon, Feb 04, 2019 at 12:19:19PM +0100, Jean-Jacques Hiblot wrote:
We need to make sure that file writes,file creation, etc. are properly
performed and do not corrupt the filesystem.
To help with
On 05/02/2019 14:45, Tom Rini wrote:
On Mon, Feb 04, 2019 at 12:19:19PM +0100, Jean-Jacques Hiblot wrote:
We need to make sure that file writes,file creation, etc. are properly
performed and do not corrupt the filesystem.
To help with this, introduce the assert_fs_integrity() function that
On Mon, Feb 04, 2019 at 12:19:19PM +0100, Jean-Jacques Hiblot wrote:
> We need to make sure that file writes,file creation, etc. are properly
> performed and do not corrupt the filesystem.
> To help with this, introduce the assert_fs_integrity() function that
> executes the appropriate fsck tool.
We need to make sure that file writes,file creation, etc. are properly
performed and do not corrupt the filesystem.
To help with this, introduce the assert_fs_integrity() function that
executes the appropriate fsck tool. It should be called at the end of any
test that modifies the
5 matches
Mail list logo