diff options
| author | https://me.yahoo.com/a/g3Ccalpj0NhN566pHbUl6i9QF0QEkrhlfPM-#b1c14 <diana@web> | 2015-02-16 20:09:25 +0100 |
|---|---|---|
| committer | GNU Hurd web pages engine <web-hurd@gnu.org> | 2015-02-16 20:09:25 +0100 |
| commit | 71aff3bc25ee51bf4bc2c5328754fa45d8c3924f (patch) | |
| tree | 64edc6f266fdce0f475822795cee70c27def2eff /community/gsoc | |
| parent | 608e4423e7f44973482fa59ee20bec029b1b8167 (diff) | |
update for rename of open_issues/unit_testing.mdwn to service_solahart_jakarta_selatan__082122541663/unit_testing.mdwn
Diffstat (limited to 'community/gsoc')
| -rw-r--r-- | community/gsoc/project_ideas/libdiskfs_locking.mdwn | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/community/gsoc/project_ideas/libdiskfs_locking.mdwn b/community/gsoc/project_ideas/libdiskfs_locking.mdwn index faac8bd9..890629a1 100644 --- a/community/gsoc/project_ideas/libdiskfs_locking.mdwn +++ b/community/gsoc/project_ideas/libdiskfs_locking.mdwn @@ -22,7 +22,7 @@ faulty paths causing these lockups. The task is systematically checking the [[hurd/libdiskfs]] code for this kind of locking issues. To achieve this, some kind of test harness has to be implemented: For example instrumenting the code to check locking correctness constantly at -runtime. Or implementing a [[open_issues/unit_testing]] framework that explicitly checks +runtime. Or implementing a [[service_solahart_jakarta_selatan__082122541663/unit_testing]] framework that explicitly checks locking in various code paths. (The latter could serve as a template for implementing unit tests in other parts of the Hurd codebase...) |