# Final step on Shell (golang) is not passing - stuck and suspect test error

**URL:** <https://forum.codecrafters.io/t/final-step-on-shell-golang-is-not-passing-stuck-and-suspect-test-error/541>\
**Category:** Challenges\
**Tags:** challenge:shell\
**Created:** [May 29, 2024, 6:23pm UTC](https://forum.codecrafters.io/t/final-step-on-shell-golang-is-not-passing-stuck-and-suspect-test-error/541 "2024-05-29T18:23:15Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![rohitpaulk](https://yyz1.discourse-cdn.com/flex003/user_avatar/forum.codecrafters.io/rohitpaulk/32/6_2.png) [@rohitpaulk](https://forum.codecrafters.io/u/rohitpaulk)\
**Post date:** [May 30, 2024, 1:03pm UTC](https://forum.codecrafters.io/t/final-step-on-shell-golang-is-not-passing-stuck-and-suspect-test-error/541/5 "2024-05-30T13:03:53Z")

</div>

Thanks for reporting this, everyone!

We’ve identified this to be a caching issue where some languages rely on `$HOME` to cache build artifacts, so when this stage executes a script with a different `HOME` it starts compiling / downloading dependencies again.

We’re still thinking about how to rectify this… Fixing each language’s reliance on `$HOME` feels very error-prone and hard for us to get right. Our current most promising idea is to change the tests for this stage to work with a fixed `HOME` value and test things like `cd ~/random_dir`.

---

_[View the full topic](https://forum.codecrafters.io/t/final-step-on-shell-golang-is-not-passing-stuck-and-suspect-test-error/541)._