the toolchain is frozen along with the sdk, so it's extremely unlikely any of that changed.  you can see in the InitSDK in both of them that they're using 2014.09.24.133933 and install no updates.

that said, why do we care about samus anymore ?  that device isn't being produced and is more than halfway through its lifespan.

if you do care, you'll want to find someone on the firmware team to investigate.  they understand all the firmware repos.

There were no firmware changes between the last working build and the broken one, so this is a hermetic build problem.

Firmware branches need to be up to roll security fixes for the life of the product.

This is pri2, since there are no known security issues with samus fw right now.

if you read the logs, you'd see there were firmware changes in there:
-  <project name="chromiumos/third_party/coreboot" path="src/third_party/coreboot" revision="c207c29fccc9d16f7818726827ba7be279525170" upstream="refs/heads/firmware-samus-6300.B"/>
+  <project name="chromiumos/third_party/coreboot" path="src/third_party/coreboot" revision="327a08946626fc792a758746d2ad2f3c0df4f31b" upstream="refs/heads/firmware-samus-6300.B"/>

https://chromium.googlesource.com/chromiumos/third_party/coreboot/+log/firmware-samus-6300.B

Indeed you are correct. I thought the waterfall would show them but I guess not.

those branches are so old they still refer to the long dead chromeos-images site.  i suspect that's why the blamelist and such don't work.  newer chromite has moved to crosland, and that shows the delta nicer:
  https://crosland.corp.google.com/log/6300.302.0..6300.303.0

i don't think it's worth backporting all this though.

Thanks! that is nicer. I'll just bookmark it.

This bug has an owner, thus, it's been triaged. Changing status to "assigned".