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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tarfix #5567

Merged
merged 4 commits into from
Jan 27, 2014
Merged

tarfix #5567

merged 4 commits into from
Jan 27, 2014

Conversation

staticfloat
Copy link
Sponsor Member

No description provided.

staticfloat added a commit that referenced this pull request Jan 27, 2014
Merge testing for compatible tar executables
@staticfloat staticfloat merged commit b12fce5 into master Jan 27, 2014
@ivarne
Copy link
Sponsor Member

ivarne commented Jan 27, 2014

Should this fix be applied to https://github.com/JuliaLang/julia/blob/master/Makefile#L287 also? It seems like it would be just as relevant there.

@staticfloat
Copy link
Sponsor Member Author

Yes, I'll go ahead and change that to a $(TAR).

@staticfloat staticfloat deleted the sf/qbit_tarfix branch January 27, 2014 21:34
@coveralls
Copy link

Coverage Status

Changes Unknown when pulling fee2372 on sf/qbit_tarfix into * on master*.

@staticfloat
Copy link
Sponsor Member Author

...........why thank you, @coveralls. Very helpful?

@mbauman
Copy link
Sponsor Member

mbauman commented May 18, 2015

@anjin - you have some sort of hash collision issue with Coveralls. If you look at the linked coveralls page, the coverage is actually from some python repository (maybe Enthought's Enstaller?).

It'd be very nice if you would verify the repository you're posting to before sending irrelevant noise to our inboxes. This sort of spurious report seems to happen about once a month on this repository alone.

@anjin
Copy link

anjin commented May 18, 2015

Are you Travis?

On Mon, May 18, 2015 at 9:58 AM, Matt Bauman [email protected]
wrote:

@anjin https://github.com/anjin - you have some sort of hash collision
issue with Coveralls. If you look at the linked coveralls page, the
coverage is actually from some python repository (maybe Enthought's
Enstaller?).

It'd be very nice if you would verify the repository you're posting to
before sending irrelevant noise to our inboxes. This sort of spurious
report seems to happen about once a month on this repository alone.


Reply to this email directly or view it on GitHub
#5567 (comment).

Lee Donahoe
LEMUR Heavy Industries
p 323.275.4588 | c 310.721.1510 | lemurheavy.com http:https://lemurheavy.com

@mbauman
Copy link
Sponsor Member

mbauman commented May 18, 2015

No, I'm not with TravisCI if that's your question. I suppose the issue could actually be upstream of you guys, but it's @coveralls that takes the flack when this happens. (See other places where this has happened: #5208 (comment), #3140 (comment), #3265 (comment), and more)

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

Successfully merging this pull request may close these issues.

None yet

6 participants