use try-with-resource

[jukzi]

to close streams.

[vogella]

FYI - updating this year is optional; I personally find it a waste of effort. If you like to do this, that is fine but in case you also find it non-value add, you can skip this step.

[vogella]

@iloveeclipse freeze period is already over or is the calender broken again? @HannesWell Maybe we could move the usage of the freeze check to use something in our repo so that we have better access to it? Like a json file defining the dates.

[laeubi]

The calendar is here: https://calendar.google.com/calendar/embed?src=prfk26fdmpru1mptlb06p0jh4s%40group.calendar.google.com&ctz=Europe%2FParis according to that we are in a Quiet period (only "stabilization", "signoff" or "promotion" ar considere "freeze-days").
If required I think it makes much sense to ask the calendar maintainers to give access to project leads and share a link that can be used to import the calendar e.g. in Thunderbird, and alike...

[github-actions]

Test Results

     240 files  ±0       240 suites  ±0   58m 23s ⏱️ + 5m 54s
  3 278 tests ±0    3 252 ✔️  - 1  24 💤 ±0  0 ❌ ±0  2 🔥 +1 
10 131 runs  ±0  10 057 ✔️  - 1  72 💤 ±0  0 ❌ ±0  2 🔥 +1 

For more details on these errors, see this check.

Results for commit 25f6550. ± Comparison against base commit e382788.

♻️ This comment has been updated with latest results.

[HannesWell]

Maybe we could move the usage of the freeze check to use something in our repo so that we have better access to it? Like a json file defining the dates.

I would prefer to have a single source of truth and if the calender is needed for other things, I would just keep it.
If necessary I agree that increasing the number of people with write access would be better.

Btw. the workflow prints a link to the console to access the calender in the Browser.

[jukzi]

only unrelated random fail #261 on win
mind to merge?

[akurtakov]

Random failing tests are with us for too long and these improvements should help to reduce "randomness" in the long term thus please merge.