There must have been some circle output that had an invalid time, which resulted in:
** (FunctionClauseError) no function clause matching in Timex.Parse.DateTime.Parser.parse!/3
The following arguments were given to Timex.Parse.DateTime.Parser.parse!/3:
# 1
nil
# 2
"{ISO:Extended}"
# 3
Timex.Parse.DateTime.Tokenizers.Default
(timex) lib/parse/datetime/parser.ex:77: Timex.Parse.DateTime.Parser.parse!/3
(circli) lib/circli/circle_api.ex:52: Circli.CircleApi.first_queued_build/2
(elixir) lib/enum.ex:1940: Enum."-reduce/3-lists^foldl/2-0-"/3
(circli) lib/circli/circle_api.ex:64: Circli.CircleApi.generate_build_results/1
(circli) lib/circli/circle_api.ex:96: Circli.CircleApi.print_build_summary/1
(elixir) lib/kernel/cli.ex:105: anonymous fn/3 in Kernel.CLI.exec_fun/2
Apparently, sometimes there is no time provided for queued_at or completed_at. This might be hard to reproduce, although I suppose it's right at the moment that a build is first listed by the API.
The next time I ran circli, it was fine.
There must have been some circle output that had an invalid time, which resulted in:
Apparently, sometimes there is no time provided for
queued_atorcompleted_at. This might be hard to reproduce, although I suppose it's right at the moment that a build is first listed by the API.The next time I ran
circli, it was fine.