From 837d1502e902814489e678ab3737cc551ad982bd Mon Sep 17 00:00:00 2001 From: Philipp Oppermann Date: Thu, 14 Jun 2018 07:51:16 +0200 Subject: [PATCH] Update post date --- .../second-edition/posts/05-integration-tests/index.md | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/blog/content/second-edition/posts/05-integration-tests/index.md b/blog/content/second-edition/posts/05-integration-tests/index.md index 8ca9cb39..5503d545 100644 --- a/blog/content/second-edition/posts/05-integration-tests/index.md +++ b/blog/content/second-edition/posts/05-integration-tests/index.md @@ -2,7 +2,7 @@ title = "Integration Tests" order = 5 path = "integration-tests" -date = 2018-05-18 +date = 2018-06-15 template = "second-edition/page.html" +++ @@ -616,8 +616,3 @@ We now have a working integration test framework and can finally start to implem ## What's next? In the next post, we will explore _CPU exceptions_. These exceptions are thrown by the CPU when something illegal happens, such as a division by zero or an access to an unmapped memory page (a so-called “page fault”). Being able to catch and examine these exceptions is very important for debugging future errors. Exception handling is also very similar to the handling of hardware interrupts, which is required for keyboard support. - - -TODO update date - -TODO update serial panic message