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

non-prerelease test fails with '/root/.ros/X/rosout.log': No such file or directoryError opening rosout log #121

Closed
130s opened this issue Feb 13, 2017 · 5 comments
Labels

Comments

@130s
Copy link
Member

130s commented Feb 13, 2017

Example sniekum/ar_track_alvar#116
Prerelease tests are passing.

@130s
Copy link
Member Author

130s commented Feb 14, 2017

Download file's storage location issue in sniekum/ar_track_alvar#116 is resolved thanks to @ipa-mdl's help.

But it still doesn't make sense to me why the error message in the title /root/.ros/X/rosout.log': No such file or directoryError opening rosout log happened and why did it get resolved at the same time, because the solution in the same ticket was about where to download the resource needed for the tests, and that has nothing to do with the location of rosout.log's location.

I won't, however, dig this deeper for now. Maybe those two locations are related somehow. We can reopen when this happens again.

@130s 130s closed this as completed Feb 14, 2017
@130s
Copy link
Member Author

130s commented Feb 15, 2017

Happening on another repo wg-perception/people#49
An example from Travis.

@130s 130s reopened this Feb 15, 2017
@mathias-luedtke
Copy link
Member

mathias-luedtke commented Feb 15, 2017

I don't see a connection, at least no hint on read-only system problems..

@130s
Copy link
Member Author

130s commented Feb 16, 2017

Yeah seems like.

I didn't mean to ask for the help @ipa-mdl -- I like to leave as much data as possible whenever I hit issues. But I always appreciate the company :)

@130s 130s closed this as completed Feb 16, 2017
@mathias-luedtke
Copy link
Member

It could have been a regression bug as well, so keep on pointing to problems :)

I am a little bit concerned that the log output is not as helpful as it should be..

@130s 130s added the invalid label Nov 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants