git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [Outreachy] Blog: Introducing myself as an intern working to convert unit test to use clar

From
Patrick Steinhardt <ps@pks.im>
Date
Dec 22, 2024, 14:41 UTC
Message-ID
<Z2glK5uJOX6ARFUa@pks.im>
In-Reply-To
<CAGedMtfDMj5P0T6x3soe3OUhRbpSw_-m1Vcm+rhDat1vvReK9w@mail.gmail.com>
On Sun, Dec 22, 2024 at 02:22:38PM +0100, Seyi Chamber wrote:
Show 25 quoted lines
> On Sun, 22 Dec 2024 at 08:23, Patrick Steinhardt <ps@pks.im> wrote:
> >
> > On Fri, Dec 20, 2024 at 11:37:23AM +0100, Seyi Chamber wrote:
> > > Hello everyone,
> > >
> > > I just published a new blog post on unit test scripts I've selected
> > > and prioritized for initial conversion to clar. I would love for you
> > > to check it out and share your opinion!
> > >
> > > Find the link here:
> > > https://seyi-kuforiji-902b48.gitlab.io/posts/week-2-prioritizing-test-scripts
> >
> > Thanks for the blog post! The initial selection looks reasonable to me.
> > I was wondering whether it would make sense to evict "t-reftable-tree.c"
> > out of the first batch and then handle all reftable-related tests in a
> > single patch series. But we've got 9 of those, some of which are quite
> > complex, so that patch series would become quite large overall. So I
> > guess it's sensible to distribute the conversion of the reftable tests
> > across different patch series.
> >
> > Patrick
> 
> I suppose I could still make that work if that's your recommendation.
> I could divide the reftable-related tests into two sets and then treat
> them together. What do you think?

I'll leave it up to you, as there is no "right" or "wrong" in this context.

Patrick
Previous: Seyi ChamberNext: Seyi Chamber
Message 4 of 9 in “Re: [Outreachy] Blog: Introducing myself as an intern working to convert unit test to use clar”
  1. Seyi ChamberDec 20, 2024
  2. Patrick SteinhardtDec 22, 2024
  3. Seyi ChamberDec 22, 2024
  4. Patrick SteinhardtDec 22, 2024
  5. Seyi ChamberDec 24, 2024
  6. Seyi ChamberJan 11, 2025
  7. Seyi ChamberJan 20, 2025
  8. Seyi ChamberFeb 11, 2025
  9. Seyi ChamberMar 11, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.