Skip to content

Stabilize two test that seem to often fail on the CI#1705

Open
laeubi wants to merge 1 commit intoeclipse-lemminx:mainfrom
laeubi:stabilize_tests
Open

Stabilize two test that seem to often fail on the CI#1705
laeubi wants to merge 1 commit intoeclipse-lemminx:mainfrom
laeubi:stabilize_tests

Conversation

@laeubi
Copy link
Copy Markdown
Contributor

@laeubi laeubi commented Nov 10, 2024

  • Use a timeout instead of static wait times
  • retry diagnostics
  • use a copy of the current state

This also reduces the test time from 5 sec to less than a second for the

TimeUnit.SECONDS.sleep(5); // HACK: to make the timing work on slow machines

Comment thread org.eclipse.lemminx/src/test/java/org/eclipse/lemminx/XMLAssert.java Outdated
@laeubi laeubi force-pushed the stabilize_tests branch 5 times, most recently from 1bcac1d to 0952504 Compare November 10, 2024 18:53
@laeubi
Copy link
Copy Markdown
Contributor Author

laeubi commented Nov 10, 2024

Seems one need to sort out what is really "unexpected" here... some of the returned diagnostics do not look that wrong given other seem to be intermediates or even valid... I'll take a look later on this, but currently it makes contributions really hard if there are random failures.

@angelozerr
Copy link
Copy Markdown
Contributor

Seems one need to sort out what is really "unexpected" here... some of the returned diagnostics do not look that wrong given other seem to be intermediates or even valid... I'll take a look later on this, but currently it makes contributions really hard if there are random failures.

I understand that it is an annoying problem, this problem should be fixed.

- Use a timeout instead of static wait times
- retry diagnostics
- use a copy of the current state

Signed-off-by: Christoph Läubrich <laeubi@laeubi-soft.de>
Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants