Skip to content
This repository has been archived by the owner on Feb 4, 2021. It is now read-only.

image demo not working on eatable #3

Closed
mikaelarguedas opened this issue Apr 11, 2017 · 5 comments
Closed

image demo not working on eatable #3

mikaelarguedas opened this issue Apr 11, 2017 · 5 comments
Assignees

Comments

@mikaelarguedas
Copy link
Member

Since eatable has been turned back on it is failing the image demo tests.
@clalancette to give context about what has been done on the node and its reactivation

CI failing tests:
http://ci.ros2.org/job/ci_windows/2534/
http://ci.ros2.org/job/ci_windows/2555/
list of builds here: http://ci.ros2.org/computer/windows_slave_eatable/builds

@clalancette
Copy link

I just took eatable offline. I added additional information to the logbook, but essentially:

  • This is our only Windows 8.1 machine.
  • It is randomly failing some tests that work fine on our other Windows (10) machines.
  • It probably needs an update to RTI Connext, and maybe some other software.

So we should probably just leave it offline until someone has time to debug the problems, and/or declare Windows 8 unsupported.

@nuclearsandwich nuclearsandwich self-assigned this Apr 11, 2017
@dhood
Copy link
Member

dhood commented Apr 18, 2017

sorry to be late to the party, I only just found this repo. my notification settings are fixed now.

Last time I saw that output for image demo tests on windows buildfarm machines, it was resolved by setting the opencv path (entry 16 in the logbook). The other test failures seem to just be flaky tests, right?

I sense that there is more context here around disabling eatable, so I am trying to get the info on paper before we forget about this.

@nuclearsandwich
Copy link
Member

sorry to be late to the party, I only just found this repo. my notification settings are fixed now.

No worries, we actually recommended folks unwatch this repo with the intention that only current the buildcopfarmer needs to be watching this space.

@mikaelarguedas
Copy link
Member Author

It probably needs an update to RTI Connext, and maybe some other software

It may not have a patched version of connext that would lead to randomly failing generated messages when running in multithreaded

There is also the more global question of: "do we target Windows8.1 support?" if yes we may want another windows8.1 machine and create different jobs for those. If not this should be upgraded to be another Windows 10 node

@dirk-thomas
Copy link
Member

dirk-thomas commented May 2, 2017

This will be obsolete with eatable being offline and scheduled to be reprovisioned with Windows 10 (see #17).

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

No branches or pull requests

5 participants