9178
66%

Ran 11 May 2018 07:33PM UTC

Jobs 1

Files 85

Run time 4s

Badge

Embed ▾

pending completion

Build # 9178

Build Type

push

travis-ci

Committed by

rolandshoemaker

Commit Message

Make datetime consistent for authz expiration (#3706)

So I took a quick stab at one possible solution for the authz expiration variance discussed over at community.letsencrypt.org/t/inconsistent-datetime-format-in-some-responses/61452

Golang's nanosecond precision results in newly created pending authz having one expires datetime, but subsequent requests have a different expires datetime due to database storage throwing away fractional second information.

  "expires": "2018-04-14T04:43:00.105818284Z",
...
  "expires": "2018-04-14T04:43:00Z",
I am not a Go expert so there might be some more widely accepted approach to accomplishing the same thing, please let me know if you would prefer a different solution.

Run Details

10019 of 16028 relevant lines covered (62.51%)

0.69 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
9	9178.9 (RUN="coverage")	11 May 2018 07:33PM UTC	0	62.51	Travis Job 9178.9

Source Files on build 9178

Detailed source file information is not available for this build.

letsencrypt / boulder / 9178
66%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 9178

letsencrypt / boulder / 9178 66%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 9178

letsencrypt / boulder / 9178
66%

README BADGES
x