-
Notifications
You must be signed in to change notification settings - Fork 1.6k
TestSPFrequency.testCategory test failure in Vagrant VM #411
Comments
The entire output of the failure as requested by Matt Taylor: |
I ran up my own Lubuntu vagrant box and set it up using the instructions on https://github.com/numenta/nupic/wiki/Install-Nupic-on-ubuntu-13.04 and all the tests passed using code from: commit e3719ae The code that failed with the Numenta VM was from: commit 23a5225 I hope this isn't a red herring caused by it being my first time environment setup. My system is: Lubuntu 13.10 64bit |
Breznak, on the 8 Nov I tried runniing up the Numenta VM and got the test failures. Since then I have also run up my own installation on Lubuntu using the wiki/Install-Nupic-on-ubuntu-13.04 intructions and all the test ran fine on that. I haven't gone back to try and get the Numenta VM since the test error. |
Ah, I see. So changing the title. Glad it runs for you somehow, so it's not a hot issue. Feel free to comment on the bug if you do retest that, or just close if you dont bother anymore. |
I'm hitting this same error. I hit it with the unit tests The common error is: More fully: This is with the Numenta VM from https://github.com/numenta/nupic/wiki/Running-Nupic-in-a-Virtual-Machine running on VirtualBox running on Windows. I haven't successfully worked around the issue. |
I did some debugging. I plan on continuing, but here's what I learned. Here's a gdb snippet that shows where this is going very badly:
If you look around, this should never happen. This function is called with type == Here's the enum in question.
So So the binaries are using different versions of an enum. I'll try to find where it's pulling the stale enum value... |
Interesting, the issue stopped reproing after I specifically ran: I might be pinpointing this incorrectly -- I ran a few other build commands today not mentioned above. But my point is that this seems to be a subtle build-ordering issue. |
...and now I synced to latest, and it's not reproing. Not even on a fresh VM. My previous comment is still correct -- I went from repro -> no repro without changing/syncing any code. Anyway, maybe something from the past week fixed the issue. |
@mtbvang Can you pull the latest, rebuild and try running tests again? I'd like to see if the problem is still occurring in your environment. |
Environment:
Test failure:
See this thread for context.
The text was updated successfully, but these errors were encountered: