.github/workflows: ci-core: print logs directly

[jmank88]

This indirect log printing is no longer necessary since we have limited standard logs again.

[jmank88]

This is not quite as simple as I first thought, since we still use -json for the scheduled runs

[erikburt]

USE_TEE is actually not supported anymore. However, it will use tee if $DEBUG is true.

So we can set debug to true when printResults is true, and it's not a scheduled event:

Suggested change

	USE_TEE: ${{ matrix.type.printResults }}
	DEBUG: ${{ matrix.type.printResults == 'true' && github.event_name != 'schedule' }}

Could also use the filtered test results when it is a scheduled run, as that uses JSON.

      - name: Print Filtered Test Results
        if: ${{ failure() && needs.filter.outputs.should-run-ci-core == 'true' && steps.run-tests.conclusion == 'failure' && github.event_name == 'schedule' }}
        run: |
          if [[ "${{ matrix.type.printResults }}"  == "true" ]]; then
            cat output.txt | gotestloghelper -ci
          fi

[jmank88]

IMHO we should try to simplify this overall. Our intention in this case is to run plain go test without a bunch of options, and in principle we shouldn't have to un-configure things to achieve that.

[erikburt]

I agree, the pipeline itself and these scripts are too complex.

I'm heads down on the test binary hashing solution, which will likely blow up this pipeline so not sure if it's worth investing a lot of time to simplify the existing one.

[Tofel]

@erikburt maybe this is good enough for now? #15395; we do have the logs we wanted: https://github.com/smartcontractkit/chainlink/actions/runs/12012195713/job/33482885604?pr=15395

[jmank88]

Closing in favor of #15395