|
You are here |
me.micahrl.com | ||
| | | | |
wsummerhill.github.io
|
|
| | | | | SecurityTube Linux Assembly Expert (SLAE) Assignment 2 | |
| | | | |
blog.djy.io
|
|
| | | | | ||
| | | | |
jmmv.dev
|
|
| | | | | About two weeks ago, I found a very interesting bug in Bazel's test output streaming functionality while writing tests for a new feature related to Ctrl+C interrupts. I fixed the bug, wrote a test for it, and... the test itself came back as flaky, which made me find another very subtle bug in the test that needed a one-line fix. This is the story of both. Bazel has a feature known as test output streaming: by default, Bazel captures the outputs (stdout and stderr) of the tests it runs, saves those in local log files, and tells the user where they are when a test fails. This is not very ergonomic when you are iterating on a test, so you can make Bazel print the output of the test as it runs by passing --test_output=streamed to the invocation. | |
| | | | |
mrcat.au
|
|
| | | [AI summary] The author plans to participate in the Advent of Code 2023 programming challenge, sharing their solutions and code in various languages while emphasizing the learning and fun aspects over leaderboard competition. | ||