Bug: Integration tests failing on main branch

[Scanf-s]

Description

Integration tests are consistently failing in the current environment when running against the main branch.

Environment

• OS: Linux(Ubuntu/WSL)
• Branch: SchoolyB/EZ:main
• Go version: 1.23.1

Steps to Reproduce

1. Clone repository: git clone https://github.com/SchoolyB/EZ.git
2. Install EZ: make install
3. Run Integration Tests: make integration-test

When I'm trying to run integration test based on SchoolyB/EZ main branch, below error occurs.

sullung@DESKTOP-1MJVMNK:~/Development/temp/EZ$ make integration-test
Building EZ...
go build -ldflags "-X main.Version=v0.39.2-3-g740ad57 -X main.BuildTime=2026-01-08_10:24:10" -o ez ./cmd/ez
Build complete! Binary: ./ez
./integration-tests/run_tests.sh
========================================
  EZ Integration Test Suite
========================================

Running PASS tests...
----------------------------------------
  core/arrays... PASS
make: *** [Makefile:61: integration-test] Error 1

The Problem

I found some failing tests on below ez scripts

• integration-tests/pass/stdlib/os.ez
• integration-tests/pass/stdlib/io.ez
• integration-tests/pass/warnings/W2010_chained_nil_access.ez

[SchoolyB]

@Scanf-s Thank you for making this issue. I believe this is valid. I have noticed this as well on occasion but for me only ocassionally io.ez and os.ez fail for me. I will look into this soon

[Scanf-s]

I’m planning to wait until this issue is settled before opening a PR for #909.

Although the implementation and unit tests are complete, the integration tests are currently failing, even on the main branch.

If you prefer, I can submit the PR for #909 first and then look into fixing #952 if my resource is available!

[SchoolyB]

I’m planning to wait until this issue is settled before opening a PR for #909.

Although the implementation and unit tests are complete, the integration tests are currently failing, even on the main branch.

If you prefer, I can submit the PR for #909 first and then look into fixing #952 if my resource is available!

I am looking into #952 right now in hopes of having a fixed merged on the upstream bugifxes/1-9-2026 branch. I have yet to recreate the issue locally today for some very odd reason even thought I 100% have had the same failing tests before.