tez-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "TezQA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TEZ-3977) Add Eric Wohlstadter's public key to KEYS
Date Tue, 07 Aug 2018 20:54:00 GMT

    [ https://issues.apache.org/jira/browse/TEZ-3977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16572320#comment-16572320

TezQA commented on TEZ-3977:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  against master revision fe22f32.

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version
3.0.1) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: https://builds.apache.org/job/PreCommit-TEZ-Build/2888//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2888//console

This message is automatically generated.

> Add Eric Wohlstadter's public key to KEYS
> -----------------------------------------
>                 Key: TEZ-3977
>                 URL: https://issues.apache.org/jira/browse/TEZ-3977
>             Project: Apache Tez
>          Issue Type: Task
>            Reporter: Eric Wohlstadter
>            Priority: Major
>         Attachments: TEZ-3977.1.patch
> {code:java}
> bash> gpg --full-generate-key
> gpg (GnuPG) 2.2.4; Copyright (C) 2017 Free Software Foundation, Inc.
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> Please select what kind of key you want:
>    (1) RSA and RSA (default)
>    (2) DSA and Elgamal
>    (3) DSA (sign only)
>    (4) RSA (sign only)
> Your selection? 1
> RSA keys may be between 1024 and 4096 bits long.
> What keysize do you want? (2048) 4096
> Requested keysize is 4096 bits       
> Please specify how long the key should be valid.
>          0 = key does not expire
>       <n>  = key expires in n days
>       <n>w = key expires in n weeks
>       <n>m = key expires in n months
>       <n>y = key expires in n years
> Key is valid for? (0) 0
> Key does not expire at all
> Is this correct? (y/N) y
> GnuPG needs to construct a user ID to identify your key.
> Real name: Eric Wohlstadter
> Email address: wohlstad@gmail.com
> Comment: CODE SIGNING KEY        
> You selected this USER-ID:
>     "Eric Wohlstadter (CODE SIGNING KEY) <wohlstad@gmail.com>"
> Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? O
> bash> gpg --send-key XXXXX
> gpg: sending key XXXXX to hkps://hkps.pool.sks-keyservers.net{code}

This message was sent by Atlassian JIRA

View raw message