-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix Error reporting and parsing (fixes #1852) #1857
Conversation
Generated by 🚫 Danger |
@jywarren YAY! Let me know when you're okay with this one, and I'll remove the error. |
Looks perfect, fantastic fix thank you @ryzokuken!
…On Dec 10, 2017 3:00 AM, "Ujjwal Sharma" ***@***.***> wrote:
@jywarren <https://github.com/jywarren> YAY! Let me know when you're okay
with this one, and I'll remove the error.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1857 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABfJxYwtpJGcpZDuz2X2NWSuqOfxI9Vks5s-4-GgaJpZM4Q8aMF>
.
|
@jywarren so, here it is. Feel free to merge this. |
@jywarren this happened:
strange. Why are there permission issues to begin with? There weren't any earlier and we didn't change anything related to the directory permissions, did we? Also, generally, I had no idea why were doing all the stuff in Lines 21 to 26 in 16e7279
Lines 22 to 24 in 16e7279
output.xml file and then run danger on the output.xml , parsing it and making a comment.
But why do we make an empty file in there? Why make the directory? Doesn't the directory already exist? What purpose does the empty file serve? |
Hi, @ryzokuken -- i inserted those lines because the Junit generation wasn't working and we saw a test error due to that directory not working. I think we can remove them and it should resolve now that you've gotten Junit working again. |
I removed them -- let's see! |
@jywarren sure, gimme a second. |
Oh, wait. You already did. 😛 Thanks |
@jywarren It worked! YAY! |
🥂 👍 💯 |
@jywarren what next? Anything you specifically wanted me to work on? |
* Fix Error reporting and parsing (fixes publiclab#1852) * Remove fraudlent failure * Update .travis.yml
Make sure these boxes are checked before your pull request is ready to be reviewed and merged. Thanks!
rake test:all
Please be sure you've reviewed our contribution guidelines at https://publiclab.org/wiki/contributing-to-public-lab-software
We have a loose schedule of reviewing and pulling in changes every Tuesday and Friday, and publishing changes on Fridays. Please alert developers on plots-dev@googlegroups.com when your request is ready or if you need assistance.
Thanks!