Skip to content

Conversation

@tmssngr
Copy link
Contributor

@tmssngr tmssngr commented Sep 3, 2024

This should cover the case that BeginBufferedPaint might fail.

@tmssngr tmssngr requested a review from niraj-modi as a code owner September 3, 2024 10:11
@github-actions
Copy link
Contributor

github-actions bot commented Sep 3, 2024

Test Results

   483 files  ±0     483 suites  ±0   8m 22s ⏱️ -17s
 4 095 tests ±0   4 085 ✅ ±0   7 💤 ±0  3 ❌ ±0 
16 173 runs  ±0  16 080 ✅ ±0  90 💤 ±0  3 ❌ ±0 

For more details on these failures, see this check.

Results for commit 2504714. ± Comparison against base commit 2ce8542.

♻️ This comment has been updated with latest results.

@tmssngr tmssngr force-pushed the feature/924-beginbufferedpaint-might-fail branch from 8173af6 to 7875692 Compare September 3, 2024 10:17
@tmssngr tmssngr force-pushed the feature/924-beginbufferedpaint-might-fail branch from 7875692 to 16fe2fd Compare September 27, 2024 09:43
@tmssngr tmssngr force-pushed the feature/924-beginbufferedpaint-might-fail branch from 16fe2fd to c48579c Compare November 8, 2024 11:43
@tmssngr
Copy link
Contributor Author

tmssngr commented Nov 8, 2024

Can somebody please merge this request? I don't think that the failing GTK tests are caused by this patch.

@BeckerWdf
Copy link
Member

So this PR fixes #924 ?

@BeckerWdf
Copy link
Member

I am not an expert on that topic and even do no work on windows. So somebody else should have a look at it.

@HeikoKlare
Copy link
Contributor

In general, the change looks sound to me. I am just wondering whether it is necessary and thus whether we should merge this change now. We are already past M3 and even though I would consider the risk of the change as low in general, at the same the affected code is quite crucial. The issue does not seem to be critical: the report has been made a year ago and no one else complained so far. So would it be sufficient to target this for 2025-03 M1? Then we have the whole three months of 2025-03 development for implicit testing by developers using Windows.

@tmssngr tmssngr force-pushed the feature/924-beginbufferedpaint-might-fail branch from c48579c to 006e1fe Compare November 26, 2024 10:58
@HeikoKlare HeikoKlare force-pushed the feature/924-beginbufferedpaint-might-fail branch 3 times, most recently from 015f8fa to db6d8e9 Compare December 2, 2024 13:06
…ring painting

This should cover the case that BeginBufferedPaint might fail.
@HeikoKlare HeikoKlare force-pushed the feature/924-beginbufferedpaint-might-fail branch from db6d8e9 to 2504714 Compare December 3, 2024 08:29
@tmssngr
Copy link
Contributor Author

tmssngr commented Dec 3, 2024

Would someone be brave enough to commit to master? Why does the Linux build fail? Shouldn't be caused by this PR.

@HeikoKlare
Copy link
Contributor

Would someone be brave enough to commit to master? Why does the Linux build fail? Shouldn't be caused by this PR.

Yes, I've just rebased the branch onto master. Linux build failures are existing and documented here: #1564
I'm just curious about the reported new Maven issues, which is why I retriggered the Jenkins build.

@HeikoKlare
Copy link
Contributor

Failing tests are unrelated and documented:

@HeikoKlare HeikoKlare merged commit 485f9db into eclipse-platform:master Dec 5, 2024
8 of 14 checks passed
@tmssngr
Copy link
Contributor Author

tmssngr commented Dec 5, 2024

Thanks for merging.

@tmssngr tmssngr deleted the feature/924-beginbufferedpaint-might-fail branch December 16, 2024 13:03
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.

3 participants