History log of /fuchsia/zircon/system/utest/fs/test-directory.cpp
Revision Date Author Comments
# d1867d4f 07-Sep-2018 George Kulakowski <kulakowski@google.com>

[compiler.h] Migrate many C++ clients of countof to fbl::count_of

The latter is safer in C++, and the former is a namespace violation in
compiler.h that eventually needs to be resolved.

Test: CQ; should be no functional change
Change-Id: I9809b9fe062fd5f07226323035bf094b3f9de798


# 3c0c8f63 02-May-2018 Doug Evans <dje@google.com>

[unittest] Use different timeouts for different test types

Small tests shouldn't have the same timeout as large tests.
So we need a way to have different values per test type.
Plus IWBN to override the default timeouts with one value
instead of one for each test type.

This patch accomplishes both by retasking the timeout value
specified by the user as the "base timeout", and then each
test type's timeout is a multiple of that.

The current values are still pretty conservative until the bots
specify a timeout more suited for them (INTK-312).
Plus there are outliers (ZX-2103, ZX-2107) that needed to be handled.
Fortunately there aren't many.

ZX-2104 #comment patch

Change-Id: Ie90ac09a35b5abf616cf2b4e3d36e9e90febe5af


# 6c4c064e 12-Mar-2018 Mark Seaborn <mseaborn@google.com>

[utest] Remove empty-string "msg" args from EXPECT/ASSERT calls in C++

The "msg" argument is optional in C++. A number of instances of
empty-string "msg" arguments have appeared since I last removed them.

This cleanup was automated.

ZX-905

Change-Id: I434d129836642216588f110d1cb161859ff3efea


# a20627cd 28-Sep-2017 Sean Klein <smklein@google.com>

[fs] Label slow filesystem tests as LARGE

Change-Id: I2ed1ed4e970756dfc159ef62e911a89c37d7c5e9


# d8f95921 05-Sep-2017 Sean Klein <smklein@google.com>

[minfs] Fix fsck bug which incorrectly flags direntry sizes

MinFS direntry records have two distinct notions of
size: First, they have a 'minimum required size for their name',
as calculated by DirentSize, but they also have a 'physical
record length', which must be greater than or equal to the
DirentSize name.

The "kMinfsMaxDirentSize" constant is the maximum calculated
value of the DirentSize length, but it may notably be less
than the record length. This patch fixes an issue with
fsck, where it makes the (invalid) assumption that
"kMinfsMaxDirentSize" refers to the maximum record length.

Regression test added, which triggers the fsck failure
without the fix.

Change-Id: I0d9293918428cfc4ef780657659c569812e851b2