make release tags about nim-chronos HOT 8 CLOSED

Nim CI which always requests latest chronos version

see important_packages: document that packages tested should ideally have recent release tags by timotheecour · Pull Request #17134 · nim-lang/Nim

from nim-chronos.

latest chronos version

I'm not sure why this makes any difference? chronos tests with master are green with Nim in the chronos repo - ie every chronos master commit is as good as a release tag.

from nim-chronos.

Not always, I guess?

from nim-chronos.

Github actions is broken for i386 currently, upstream issues, causing partial failures - having a release tag unfortunately wouldn't resolve that.

See actions/runner-images#2951 (comment)

from nim-chronos.

OK, thanks

from nim-chronos.

I suspect making release tags isn't really a problem, just don't think they will help with this particular situation.

from nim-chronos.

This shows another failed case

nim-lang/Nim#17495

https://github.com/nim-lang/Nim/pull/17495/checks?check_run_id=2182688051

  PASS: [3/42] chroma c                                                     ( 4.13 sec)
  FAIL: chronicles c
  Test "chronicles" in category "nimble-packages"
  Failure: reBuildFailed
  nim c -o:chr -r chronicles.nim
  Hint: used config file '/Users/runner/work/Nim/Nim/config/nim.cfg' [Conf]
  Hint: used config file '/Users/runner/work/Nim/Nim/config/config.nims' [Conf]
  Hint: used config file '/Users/runner/work/Nim/Nim/pkgstemp/chronicles/nim.cfg' [Conf]
  ......................................................
  /Users/runner/.nimble/pkgs/chronos-3.0.0/chronos/asyncmacro2.nim(185, 1) template/generic instantiation from here
  /Users/runner/.nimble/pkgs/chronos-3.0.0/chronos/asyncmacro2.nim(187, 55) Error: can raise an unlisted exception: ref ValueError

from nim-chronos.

This shows another failed case

this is a chronicles failure though, as an incompatible chronos change was introduced (hence the new chronos major release number)

from nim-chronos.