Bump d3-time from 1.1.0 to 3.1.0

[dependabot]

Bumps d3-time from 1.1.0 to 3.1.0.

Release notes

Sourced from d3-time's releases.

v3.1.0

• Add d3.unixDay and d3.unixDays. #58
• Adopt d3.unixDay in place of d3.utcDay for d3.utcTicks to ensure uniform tick spacing.

v3.0.0

• Adopt type: module. #50

This package now requires Node.js 12 or higher. For more, please read Sindre Sorhus’s FAQ.

v2.1.1

• Fix crash in d3.timeTicks and d3.utcTicks when the given interval is invalid.
• Document that d3.timeTickInterval and d3.utcTickInterval return null when the given interval is invalid.

v2.1.0

• Add d3.timeTicks and d3.utcTicks.
• Add d3.timeTickInterval and d3.utcTickInterval.
• Update dependencies.

v2.0.0

• This release adopts ES2015 language features such as for-of and drops support for older browsers, including IE. If you need to support pre-ES2015 environments, you should stick with d3-time 1.x or use a transpiler.

Commits

• d66bba6 3.1.0
• d718202 localize let
• e32ec63 adopt const, arrow; drop default exports
• e89a467 Update README
• a80c652 update dependencies
• c92ddc6 2022
• 850c1c2 add unixDay interval (#58)
• 3e9b59b Change "due on" to "due to" (#54)
• 08cdaa6 3.0.0
• ee72b8a fix #51; extract copyrights from license
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[kalikiana]

t/ui/13-admin.t (Wstat: 256 Tests: 16 Failed: 1)
  Failed test:  13
  Non-zero exit status: 1
Files=1, Tests=16, 44.5856 wallclock secs ( 0.06 usr  0.00 sys + 20.92 cusr  0.76 csys = 21.74 CPU)
Result: FAIL
Calling retry hook ./tools/delete-coverdb-folder
Deleting cover_db_unstable_t_ui_13-admin.t/
Retry 4 of 5 …
[12:59:01] t/ui/13-admin.t .. 12/? 
    #   Failed test 'YAML got a final linebreak'
    #   at t/ui/13-admin.t line 554.
    #          got: 'products: {}
    # scenarios: {}
    # '
    #     expected: 'products: {}
    # scenarios: {}
    #  # additional comment
    # '
    # 0

    #   Failed test 'conflict reported'
    #   at t/ui/13-admin.t line 563.
    #                   'YAML saved!
    # 1
    # @@ -1,2 +1,3 @@
    # 2
    #  products: {}
    # 3
    #  scenarios: {}
    # 4
    # + # additional comment # one more comment'
    #     doesn't match '(?^:Template was modified)'
    # 0
    # Looks like you failed 2 tests of 28.
[12:59:01] t/ui/13-admin.t .. 13/? 
#   Failed test 'edit job templates'
#   at t/ui/13-admin.t line 578.
[12:59:01] t/ui/13-admin.t .. 16/? # Looks like you failed 1 test of 16.
                                   [12:59:01] t/ui/13-admin.t .. Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/16 subtests 
[12:59:47]

Test Summary Report
-------------------
t/ui/13-admin.t (Wstat: 256 Tests: 16 Failed: 1)
  Failed test:  13
  Non-zero exit status: 1

[kalikiana]

[12:59:48] t/ui/13-admin.t .. 12/? 
    #   Failed test 'YAML got a final linebreak'
    #   at t/ui/13-admin.t line 554.
    #          got: 'products: {}
    # scenarios: {}
    # '
    #     expected: 'products: {}
    # scenarios: {}
    #  # additional comment
    # '
    # 0

    #   Failed test 'conflict reported'
    #   at t/ui/13-admin.t line 563.
    #                   'YAML saved!
    # 1
    # @@ -1,2 +1,3 @@
    # 2
    #  products: {}
    # 3
    #  scenarios: {}
    # 4
    # + # additional comment # one more comment'
    #     doesn't match '(?^:Template was modified)'
    # 0
    # Looks like you failed 2 tests of 28.
[12:59:48] t/ui/13-admin.t .. 13/? 
#   Failed test 'edit job templates'
#   at t/ui/13-admin.t line 578.
[12:59:48] t/ui/13-admin.t .. 16/? # Looks like you failed 1 test of 16.

[kalikiana]

I tre-triggered once more after all tests seems to have passed because I'm wondering if something is affecting stability of the tests, possibly introduced here.

[Martchus]

I'm also wondering about this. Those failures are definitely unrelated to the code change. They are also different from the two other problems I worked on as part of https://progress.opensuse.org/issues/157540. (Those failures I actually haven't seen anymore since my related PRs were merged.) This means the number of recent sporadic failures sums up a lot recently. Maybe just a coincidence, though.

[okurz]

I will look into statistics about t/ui/13-admin.t