Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revise testing policy with labels #57

Merged
merged 2 commits into from
Nov 10, 2022

Conversation

hlandau
Copy link
Member

@hlandau hlandau commented Oct 20, 2022

First draft. Let me know your thoughts. I've tried to avoid overengineering this for now.

@hlandau hlandau added the policy change A change to a policy is being proposed label Oct 20, 2022
@hlandau hlandau self-assigned this Oct 20, 2022
policies/testing.md Outdated Show resolved Hide resolved
policies/testing.md Outdated Show resolved Hide resolved
Copy link
Member

@mattcaswell mattcaswell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

policies/testing.md Show resolved Hide resolved
policies/testing.md Show resolved Hide resolved
@hlandau
Copy link
Member Author

hlandau commented Oct 21, 2022

Updated.

- `tests: deferred`, where the tests are required by the testing policy
but it is intended to add these tests in a subsequent PR. The label should
be removed (for example from a closed PR) once subsequent tests have
been merged.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How do we deal with situations where the PR author considers that the current test suite is sufficient?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this would come under tests: present.

Copy link
Member

@slontis slontis Oct 21, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this fail to merge without one of these labels being set, going to display a relevant error?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How would you want to do this. It would require the GHE hooks to look at the PRs in the merged commits which I do not think we want.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this would come under tests: present.

It may also be "tests: exempted". For example a refactor is specifically exempted.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree with @t8m re automatic checks, because of all the churn (and because github has a 5s time limit on pre-receive hooks, where those checks need to be placed)

Copy link
Member

@t8m t8m left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is a good start for now.

labels must be applied:

- `tests: present`, to be added where suitable tests are included in the same PR.
- `hold: tests needed`, where the testing policy requires tests but they are not
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do some of these tests labels need explicit statements by each approver (I agree with the label X).
(Like we do for trivial)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it should be up to the approver to disagree with the choice.

@t8m t8m added the discussed The issue/pr was discussed by the OTC label Oct 25, 2022
@hlandau
Copy link
Member Author

hlandau commented Nov 7, 2022

It's been 18 days, so I'm now raising the vote on this. cc @openssl/otc

topic: Approve the proposed test labelling policy (technical-policies#57)
Proposed by Hugo Landau
Public: yes
opened: 2022-11-07
closed: 
accepted:  yes/no  (for: X, against: Y, abstained: Z, not voted: T)

  Dmitry     [  ]
  Matt       [  ]
  Pauli      [  ]
  Tim        [  ]
  Hugo       [+1]
  Richard    [  ]
  Shane      [  ]
  Tomas      [  ]
  Kurt       [  ]
  Matthias   [  ]
  Nicola     [  ]

@t8m
Copy link
Member

t8m commented Nov 7, 2022

Vote: [+1]

@t8m t8m added the ready to vote The policy change proposal is ready to be voted on by the OTC label Nov 7, 2022
@t-j-h
Copy link
Member

t-j-h commented Nov 7, 2022

Vote [0]

@mattcaswell
Copy link
Member

Vote: [+1]

@kroeckx
Copy link
Member

kroeckx commented Nov 7, 2022

Voting +1

@paulidale
Copy link
Contributor

Vote: [+1]

@slontis
Copy link
Member

slontis commented Nov 7, 2022 via email

@beldmit
Copy link
Member

beldmit commented Nov 7, 2022

Vote: [+1]

1 similar comment
@mspncp
Copy link
Contributor

mspncp commented Nov 7, 2022

Vote: [+1]

@mspncp
Copy link
Contributor

mspncp commented Nov 7, 2022

(Side Note: @hlandau it would be nice if you could follow the current coloring practice for the labels, i.e., reuse the existing red color for the hold: tests needed label (the hex value appears and can be copy&pasted when you 'edit' one of the existing labels) and choose a new, easily distinguishable color of your liking for the new tests: * labels.)

@hlandau
Copy link
Member Author

hlandau commented Nov 8, 2022

(Side Note: @hlandau it would be nice if you could follow the current coloring practice for the labels, i.e., reuse the existing red color for the hold: tests needed label (the hex value appears and can be copy&pasted when you 'edit' one of the existing labels) and choose a new, easily distinguishable color of your liking for the new tests: * labels.)

Agreed, this is my plan: red for the hold, something visually distinct for the other test labels.

@hlandau
Copy link
Member Author

hlandau commented Nov 10, 2022

Since the outcome of the vote is now a foregone conclusion, this vote can now be closed.

topic: Approve the proposed test labelling policy (technical-policies#57)
Proposed by Hugo Landau
Public: yes
opened: 2022-11-07
closed: 2022-11-10
accepted:  yes  (for: 8, against: 0, abstained: 1, not voted: 2)

  Dmitry     [+1]
  Matt       [+1]
  Pauli      [+1]
  Tim        [ 0]
  Hugo       [+1]
  Richard    [  ]
  Shane      [+1]
  Tomas      [+1]
  Kurt       [+1]
  Matthias   [+1]
  Nicola     [  ]

@romen
Copy link
Member

romen commented Nov 10, 2022

Vote: [+0]

@t8m
Copy link
Member

t8m commented Nov 10, 2022

I've immediately realized that we could avoid some labeling pollution by not requiring the test: exempted label on PRs that are just triaged: documentation or triaged: cleanup or triaged: design or maybe even triaged: refactor.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussed The issue/pr was discussed by the OTC policy change A change to a policy is being proposed ready to vote The policy change proposal is ready to be voted on by the OTC
Projects
None yet
Development

Successfully merging this pull request may close these issues.