Skip to content

Conversation

jgfoster
Copy link
Member

As recommended here to fix #288. This seems to fix the problem viewing the compile errors generated during a GitLab Action.

@ianfixes
Copy link
Collaborator

ianfixes commented Apr 5, 2021

I'm not sure why this would fix the problem. Is there a confounding variable here?

If you add the foo test you showed in #288 , does the compile error actually appear in the build logs?

@jgfoster
Copy link
Member Author

jgfoster commented Apr 5, 2021

@jgfoster
Copy link
Member Author

jgfoster commented Apr 5, 2021

Compare to line 703 of https://github.com/Arduino-CI/arduino_ci/runs/2266807902. I don't understand what is going on, but it just seemed odd to me to have a before(:all) and an after(:each). This wasn't balanced and I found an article that said not to use before(:all) unless you knew what you were doing (and I don't!). Since the change fixed it I was content that I was at least doing more than reporting a problem. But, I'd like someone who understands it to validate it as a reasonable solution.

@ianfixes ianfixes mentioned this pull request Apr 5, 2021
@ianfixes
Copy link
Collaborator

ianfixes commented Apr 5, 2021

Note to self,

I have your fix in #296

Thanks for the line numbers, this test gets reported in 2 places and I was originally looking at the wrong one. These build logs are enormous.

@jgfoster jgfoster merged commit cf155e7 into Arduino-CI:master Oct 3, 2021
@jgfoster jgfoster deleted the report_compile_errors branch October 3, 2021 22:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants