Deployment Completed with Errors

[alex42]

The day before yesterday, we were deploying code (not as a startup, just from Robot Main so we could do front panel debugging, and also to test the unlikely theory that loading code as a startup was causing a weird error we were having where the cRIO would switch every few seconds between working and thinking it had no code), and at the end of the process the dialog box said "deployment completed with errors" and so of course the code didn't actually run. We tried again, and were of course told the cRIO was already in use. So we rebooted the cRIO and tried again (twice), and both times it gave us "code deployed with errors". So we reimaged the cRIO, and then it worked. Yesterday evening the same problem showed up, and we fixed it in the same way. Does anyone know what might be causing this and what might work as a permanent fix? For the record, the no code error I mentioned we were also fixing temporarily through reimaging the cRIO and it wasn't manifesting itself at either time when this error showed up.

[Mark McLeod]

The next time that happens take note of what the error is.

[alex42]

We looked for the error. We couldn't find it. Admittedly, there is a lot of stuff that gets listed in that window, so we might have accidentally scrolled past it, but you'd think that if there was an error that would prevent it from running it would be easy to find since it would be near the bottom. Although in between the two times this problem happened there was one time when something in bold flashed past the screen, but when I scrolled up it wasn't there, and then the deployment completed normally.

[Acshi]

I have also gotten this same exact error, or, that is, lack of an actual error. I have just gotten by for now by running as startup, though it takes considerably longer to make a build than to just click "run."

Maybe there is a log somewhere that actual details might be put? This problem reminds me of how earlier I had a sort of opposite problem where "run" would work just fine, but "run as startup" would give me an error complaining about the real-time deployment not being built, though it just was, with no further explanation.