| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Akshat Jaimini <destrex271(at)gmail(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-www(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Permission to allow testing harness to send error reports for pgweb directly to mailing list. |
| Date: | 2023-10-05 15:02:39 |
| Message-ID: | 7F99AF5A-8D5D-47A3-B238-4E34004C3DFE@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
> On 3 Oct 2023, at 21:30, Akshat Jaimini <destrex271(at)gmail(dot)com> wrote:
> > That is, if it finds the same issue on a later run, it must not re-send the same thing. How does it work in regards to that today?
>
> As per the current flow whenever a new commit is pushed to the pgweb repo, the tests are executed. If some tests fail, an error report is sent with the information of all the failed tests. So if that particular issue has been resolved, the same report won't be sent but if some other commit is pushed without resolving that particular issue then that particular error will be reported again.
That doesn't seem terribly great, while bugs and errors should be fixed when
found, sending reports of them repeatedly risk reporting-fatigue. Publishing
this report to a website would handle that I think.
One question, would this test harness detect and report potential security
issues like XSS? If so we should probably limit the audience of the report..
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Akshat Jaimini | 2023-10-06 06:05:01 | Re: Permission to allow testing harness to send error reports for pgweb directly to mailing list. |
| Previous Message | Magnus Hagander | 2023-10-04 16:30:52 | Re: Mailing list subscription's mail delivery delays? |