Skip to content

x/crypto/acme: TestWithPebble/TLSALPN01-Issuance failures #74437

Open
@gopherbot

Description

@gopherbot
#!watchflakes
default <- pkg == "golang.org/x/crypto/acme" && test == "TestWithPebble/TLSALPN01-Issuance"

Issue created automatically to collect these failures.

Example (log):

=== RUN   TestWithPebble/TLSALPN01-Issuance
=== PAUSE TestWithPebble/TLSALPN01-Issuance
=== CONT  TestWithPebble/TLSALPN01-Issuance
    pebble_test.go:738: fetching github.com/letsencrypt/pebble/v2@v2.7.0
2025/06/30 16:57:02 building pebble
2025/06/30 16:57:02 building pebble
2025/06/30 16:57:08 building pebble-challtestsrv
2025/06/30 16:57:08 building pebble-challtestsrv
2025/06/30 16:57:09 pebble dir: /home/swarming/.swarming/w/ir/x/w/gopath/pkg/mod/github.com/letsencrypt/pebble/v2@v2.7.0
2025/06/30 16:57:09 config file: /home/swarming/.swarming/w/ir/x/t/pebble-config-2189757696.json
...
--- FAIL: TestWithPebble/TLSALPN01-Issuance (12.15s)
Pebble 2025/06/30 16:57:14 Attempting to validate w/ HTTP: http://www.example.com:5563/.well-known/acme-challenge/9pKW3-BNiyGADjsBLLssgMJU7NOsj2p-KB7USW5BaZg
2025/06/30 16:57:14 challHTTPServer: handling GET to /.well-known/acme-challenge/9pKW3-BNiyGADjsBLLssgMJU7NOsj2p-KB7USW5BaZg from 127.0.0.1:45072
Pebble 2025/06/30 16:57:14 authz u6XDpOVcxLywFZxSg38zrNiFfwYEdCnWAi_PP4dR3ZE set VALID by completed challenge oDgy7Bm_o0MOhl_0ieX-tebLE2IruftQNEOmvmyRJ8Y
Pebble 2025/06/30 16:57:14 HEAD /nonce-plz -> calling handler()
Pebble 2025/06/30 16:57:14 POST /my-order/ -> calling handler()
Pebble 2025/06/30 16:57:15 Attempting to validate w/ HTTP: http://example.com:5563/.well-known/acme-challenge/ytz3lru4wbL8mmJ0alOaLun7Og972gP0e10JIQroKq8
Pebble 2025/06/30 16:57:15 Attempting to validate w/ HTTP: http://example.com:5563/.well-known/acme-challenge/ytz3lru4wbL8mmJ0alOaLun7Og972gP0e10JIQroKq8
Pebble 2025/06/30 16:57:15 Attempting to validate w/ HTTP: http://example.com:5563/.well-known/acme-challenge/ytz3lru4wbL8mmJ0alOaLun7Og972gP0e10JIQroKq8
2025/06/30 16:57:15 challHTTPServer: handling GET to /.well-known/acme-challenge/ytz3lru4wbL8mmJ0alOaLun7Og972gP0e10JIQroKq8 from 127.0.0.1:45084
...
Pebble 2025/06/30 16:57:16 HEAD /nonce-plz -> calling handler()
Pebble 2025/06/30 16:57:16 POST /my-order/ -> calling handler()
Pebble 2025/06/30 16:57:16 POST /finalize-order/ -> calling handler()
Pebble 2025/06/30 16:57:17 Order vL_TAV0AbFqRA6j3fBF7Pr8UigKYEOZNpUvYf7INAcY is fully authorized. Processing finalization
Pebble 2025/06/30 16:57:17 POST /my-order/ -> calling handler()
Pebble 2025/06/30 16:57:17 Issued certificate serial 5c36a53a9b55f03b for order vL_TAV0AbFqRA6j3fBF7Pr8UigKYEOZNpUvYf7INAcY
Pebble 2025/06/30 16:57:22 POST /my-order/ -> calling handler()
Pebble 2025/06/30 16:57:22 POST /certZ/ -> calling handler()
2025/06/30 16:57:22 verified 1 path(s) from issued leaf certificate to Pebble root CA
2025/06/30 16:57:22 challHTTPServer: shutting down

watchflakes

Metadata

Metadata

Assignees

No one assigned

    Labels

    NeedsInvestigationSomeone must examine and confirm this is a valid issue and not a duplicate of an existing one.

    Type

    No type

    Projects

    Status

    No status

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions