Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Latest source hits error if UI test has a failure #391

Open
ChrisMash opened this issue Mar 1, 2024 · 1 comment
Open

Latest source hits error if UI test has a failure #391

ChrisMash opened this issue Mar 1, 2024 · 1 comment

Comments

@ChrisMash
Copy link

ChrisMash commented Mar 1, 2024

A project I work on installed xcpretty from the latest source in CI (not sure why, it doesn't after hitting this issue 馃榿)

Our tests started hitting the following error when piping the output of xcodebuild (Xcode 15, running UI tests) to xcpretty when one of the tests failed:

tools/lib/xcpretty/parser.rb:366:in `parse': uninitialized constant XCPretty::Parser::ERB (NameError)
        formatter.format_failing_test($2, $3, ERB::Util.html_escape($4), $1)
                                                 ^^^^^^
	from /Users/vagrant/.mobile-sdk/tools/lib/xcpretty/formatters/formatter.rb:88:in `pretty_format'
	from /Users/vagrant/.mobile-sdk/tools/lib/xcpretty/printer.rb:19:in `pretty_print'
	from /Users/vagrant/.mobile-sdk/tools/bin/xcpretty:84:in `block in <main>'
	from /Users/vagrant/.mobile-sdk/tools/bin/xcpretty:83:in `each_line'
	from /Users/vagrant/.mobile-sdk/tools/bin/xcpretty:83:in `<main>'

It was working fine previously, until the xcpretty source was updated the other day

@ChrisMash
Copy link
Author

I imagine this is the commit that did it: 16a96b7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant