Skip to content

Bump Maven to 3.9.0 - #2972

Merged
scordio merged 1 commit into
mainfrom
maven_3.9
Mar 4, 2023
Merged

scordio merged 1 commit into
mainfrom
maven_3.9

Conversation

@scordio

@scordio scordio commented Mar 4, 2023

Copy link
Copy Markdown
Member

No description provided.

@github-actions

github-actions Bot commented Mar 4, 2023 •

Copy link
Copy Markdown

JUnit test results

  3 998 files  ±0    3 998 suites  ±0   53s ⏱️ +4s
19 311 tests ±0  19 292 ✔️ ±0  19 💤 ±0  0 ❌ ±0 
19 408 runs  ±0  19 388 ✔️ ±0  20 💤 ±0  0 ❌ ±0 

Results for commit d78b879. ± Comparison against base commit 7945673.

This pull request removes 1233 and adds 1125 tests. Note that renamed tests count towards both.


  

  b
  -1000000000-01-01T00:00:00Z
  07:10
  07:10Z
  07:23
  07:23Z
  2017-03-08T07:10
  2017-03-08T07:10-05:00[America/New_York]
…
AbstractTemporalAssert isCloseTo ‑ should fail if actual is null (ArgumentsAccessor)[1] org.assertj.core.api.InstantAssert@1, org.assertj.core.api.InstantAssert@1, org.assertj.core.data.TemporalUnitWithinOffset@51, 2017-03-12T07:12:00Z, 2017-03-12T07:12:00Z, 2017-03-08T07:10:00Z, 2017-03-08T07:10:00Z, 
Expecting actual:
  2017-03-12T07:10:00Z
to be close to:
  2017-03-08T07:10:00Z
within 50 Hours but difference was 96 Hours, null
AbstractTemporalAssert isCloseTo ‑ should fail if actual is null (ArgumentsAccessor)[2] org.assertj.core.api.InstantAssert@1, org.assertj.core.api.InstantAssert@1, org.assertj.core.data.TemporalUnitWithinOffset@21, 2017-03-12T07:10:00.001Z, 2017-03-12T07:10:00.001Z, -1000000000-01-01T00:00:00Z, -1000000000-01-01T00:00:00Z, 
Expecting actual:
  2017-03-12T07:10:00Z
to be close to:
  -1000000000-01-01T00:00:00Z
within 2 Millis but difference was PT8765837682367H10M, null
AbstractTemporalAssert isCloseTo ‑ should fail if actual is null (ArgumentsAccessor)[3] org.assertj.core.api.LocalDateTimeAssert@1, org.assertj.core.api.LocalDateTimeAssert@1, org.assertj.core.data.TemporalUnitWithinOffset@51, 2017-03-10T07:12, 2017-03-10T07:12:00, 2017-03-08T07:10, 2017-03-08T07:10:00, 
Expecting actual:
  2017-03-12T07:10
to be close to:
  2017-03-08T07:10
within 50 Hours but difference was 96 Hours, null
AbstractTemporalAssert isCloseTo ‑ should fail if actual is null (ArgumentsAccessor)[4] org.assertj.core.api.LocalDateAssert@1, org.assertj.core.api.LocalDateAssert@1, org.assertj.core.data.TemporalUnitWithinOffset@22, 2017-03-10, 2017-03-10, 2017-03-27, 2017-03-27, 
Expecting actual:
  2017-03-12
to be close to:
  2017-03-27
within 3 Days but difference was 15 Days, org.assertj.core.data.TemporalUnitWithinOffset@20
AbstractTemporalAssert isCloseTo ‑ should fail if actual is null (ArgumentsAccessor)[5] org.assertj.core.api.LocalTimeAssert@1, org.assertj.core.api.LocalTimeAssert@1, org.assertj.core.data.TemporalUnitWithinOffset@24, 07:12, 07:12:00, 07:23, 07:23:00, 
Expecting actual:
  07:10
to be close to:
  07:23
within 5 Minutes but difference was 13 Minutes, org.assertj.core.data.TemporalUnitWithinOffset@20
AbstractTemporalAssert isCloseTo ‑ should fail if actual is null (ArgumentsAccessor)[6] org.assertj.core.api.OffsetDateTimeAssert@1, org.assertj.core.api.OffsetDateTimeAssert@1, org.assertj.core.data.TemporalUnitWithinOffset@29, 2017-03-12T07:12Z, 2017-03-12T07:12:00Z, 2017-03-12T07:23Z, 2017-03-12T07:23:00Z, 
Expecting actual:
  2017-03-12T07:10Z
to be close to:
  2017-03-12T07:23Z
within 10 Minutes but difference was 13 Minutes, null
AbstractTemporalAssert isCloseTo ‑ should fail if actual is null (ArgumentsAccessor)[7] org.assertj.core.api.ZonedDateTimeAssert@1, org.assertj.core.api.ZonedDateTimeAssert@1, org.assertj.core.data.TemporalUnitLessThanOffset@7e, 2017-03-10T07:12-05:00[America/New_York], 2017-03-10T07:12:00-05:00[America/New_York], 2017-03-08T07:10-05:00[America/New_York], 2017-03-08T07:10:00-05:00[America/New_York], 
Expecting actual:
  2017-03-12T07:10-04:00[America/New_York]
to be close to:
  2017-03-08T07:10-05:00[America/New_York]
by less than 95 Hours but difference was 95 Hours, null
AbstractTemporalAssert isCloseTo ‑ should fail if actual is null (ArgumentsAccessor)[8] org.assertj.core.api.OffsetTimeAssert@1, org.assertj.core.api.OffsetTimeAssert@1, org.assertj.core.data.TemporalUnitWithinOffset@21, 07:12Z, 07:12:00Z, 07:23Z, 07:23:00Z, 
Expecting actual:
  07:10Z
to be close to:
  07:23Z
within 2 Minutes but difference was 13 Minutes, org.assertj.core.data.TemporalUnitWithinOffset@20
AbstractTemporalAssert isCloseTo ‑ should fail if offset parameter is null (ArgumentsAccessor)[1] org.assertj.core.api.InstantAssert@1, org.assertj.core.api.InstantAssert@1, org.assertj.core.data.TemporalUnitWithinOffset@51, 2017-03-12T07:12:00Z, 2017-03-12T07:12:00Z, 2017-03-08T07:10:00Z, 2017-03-08T07:10:00Z, 
Expecting actual:
  2017-03-12T07:10:00Z
to be close to:
  2017-03-08T07:10:00Z
within 50 Hours but difference was 96 Hours, null
AbstractTemporalAssert isCloseTo ‑ should fail if offset parameter is null (ArgumentsAccessor)[2] org.assertj.core.api.InstantAssert@1, org.assertj.core.api.InstantAssert@1, org.assertj.core.data.TemporalUnitWithinOffset@21, 2017-03-12T07:10:00.001Z, 2017-03-12T07:10:00.001Z, -1000000000-01-01T00:00:00Z, -1000000000-01-01T00:00:00Z, 
Expecting actual:
  2017-03-12T07:10:00Z
to be close to:
  -1000000000-01-01T00:00:00Z
within 2 Millis but difference was PT8765837682367H10M, null
…

♻️ This comment has been updated with latest results.

@scordio
scordio merged commit 5da96a3 into main Mar 4, 2023
@scordio
scordio deleted the maven_3.9 branch March 4, 2023 17: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.

1 participant