[CT-166] [Bug] accepted_values test causing OSError: File name too long

[treeforest456]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

We have 12 accepted values defined in the accepted_values test list. When running this, it gives this OSError

OSError: [Errno 36] File name too long: '/home/********/project/project-name/target/test.folder.source_accepted_values_very_long_accepted_values_strings.123456789.html'

Expected Behavior

Maybe a better way to generate test file names? Or maybe document somewhere that there could be a limit of number of accepted values defined in the list?

Steps To Reproduce

No response

Relevant log output

No response

Environment

- OS: macOS Big Sur, version 11.5.2
- Python: 3.9.5
- dbt: 1.0.0

What database are you using dbt with?

snowflake

Additional Context

No response

[nathaniel-may]

Hi, @treeforest456! Thanks for the report, and I'm sorry to hear you're having issues running tests. We have run into issues with the way we internally uniquely identify test nodes before and it seems the file path that is too long for your file system is caused in part by the unique identifier being too large.

I left a comment on a previous issue to propose a long-term fix, and I wanted to point you to a proposed short-term fix in this ticket which is identified as a good first issue for a community PR, and I believe would solve your issue as well.

Unfortunately, I cannot think of any workarounds for your particular issue that do not involve a code change to dbt.

Since this ticket specifically calls out the inability to write test results because of the filepath length, I do not believe this issue is a duplicate and will leave it open until resolved.

[github-actions]

This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please remove the stale label or comment on the issue, or it will be closed in 7 days.

[github-actions]

Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest; add a comment to notify the maintainers.