-
Notifications
You must be signed in to change notification settings - Fork 15
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
Guard against infinite loops - add timeout somehow if a test gets stuck? #25
Comments
If BlockManagerImpl doesn't have |
Saw another case of an MTE test getting stuck, this time in Rails, with a bit more maybe-interesting logging (I've snipped some "compacting cache" blocks - after this stage it just gets worse with the same stuff and eventually shows nothing else):
|
I tried to do this at the Jupiter configuration level in MovingBlocks/Terasology#4579 Even though I thought I confirmed it would cancel tests (I set it to a very short value to check), it's been ineffective when I ran in to stalling ItemPipes tests in real test runs. Don't know if I goofed up the configuration somehow, or if there's something specific about the way those tests get stuck that make Jupiter's methods unsuccessful. |
Specific example: Terasology/SimpleFarming#97
One theory is something goes weird and the MTE test just keeps generating chunks forever, which prints one of those log snippets about compacting the chunk cache every tick, which might be the only indication that something is still happening, otherwise it would just appear to hang.
I've seen similar cases elsewhere. For instance http://jenkins.terasology.io/teraorg/job/Terasology/job/engine/view/change-requests/job/PR-4036/ related to MovingBlocks/Terasology#4036 for some reason got stuck several times for hours on end. One example printed this a bunch (although not nearly as much as the SimpleFarming PR):
11:50:39.535 [Test worker] ERROR o.t.w.b.internal.BlockManagerImpl - Attempt to fetch block with unknown uri 'engine:air'
It may not be an issue specific to the MTE, could be some underlying issue with environment-based tests. Not sure which actual test stalls for SimpleFarming, although the engine one is
StorageManagerTest extends TerasologyTestingEnvironment
so yeah not MTE, but maybe both hit that environment class?The text was updated successfully, but these errors were encountered: