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.

Sign up for GitHub

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

Jump to bottom

Test IndexingMemoryControllerTests#testIndexBufferSizeUpdateAfterCreationRemoval fails post #10452 #10584

Closed
kimchy opened this issue Apr 13, 2015 · 0 comments · Fixed by #10586
Closed

Test IndexingMemoryControllerTests#testIndexBufferSizeUpdateAfterCreationRemoval fails post #10452 #10584

kimchy opened this issue Apr 13, 2015 · 0 comments · Fixed by #10586
Assignees
@s1monw

Comments

@kimchy
Copy link
Member

kimchy commented Apr 13, 2015

I was looking at a test failure to see if it relates to my change with the JVM stats aspect. Turns out it didn't, but managed to find the commit that did (#10452). Still did not chase it down into why. Running only the test on IntelliJ with -Dtests.seed=F617D748C91B4DD4 causes it to fail on my machine every time, but this for some reason doesn't repro it (still not sure why, weird):

mvn clean test -Dtests.seed=F617D748C91B4DD4 -Dtests.class=org.elasticsearch.indices.memory.IndexingMemoryControllerTests -Dtests.method="testIndexBufferSizeUpdateAfterCreationRemoval" -Dtests.locale=uk -Dtests.timezone=America/Indiana/Tell_City -Dtests.processors=4
bleskes added a commit that referenced this issue Apr 14, 2015
@bleskes
Test: mute testIndexBufferSizeUpdateAfterCreationRemoval
773d64c 
see #10584
s1monw added a commit to s1monw/elasticsearch that referenced this issue Apr 14, 2015
@s1monw
[CORE] Move back to single EngineConfig
88026ca 
We need to preserve settings (yet transient) even though the engine is not yet
started. This commit moves back to a single EngineConfig to simplify IndexShard
and settings state.

Closes elastic#10584
@s1monw s1monw mentioned this issue Apr 14, 2015
Merged
s1monw added a commit to s1monw/elasticsearch that referenced this issue Apr 14, 2015
@s1monw
[CORE] Move back to single EngineConfig
0fcd31b 
We need to preserve settings (yet transient) even though the engine is not yet
started. This commit moves back to a single EngineConfig to simplify IndexShard
and settings state.

Closes elastic#10584
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@s1monw s1monw

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Move back to single EngineConfig s1monw/elasticsearch
3 participants
@kimchy @kevinkluge @s1monw