MIME-Version: 1.0
References: 
 <CAMaW3VgbJmp8BQw_QUshk4JfFhOco--ymhEwjwGRTvftzqpiZg@mail.gmail.com>
 <CAMaW3ViEK3=hkR9bEeaHoNFfos5s_xnNMqdXZUGVqL_k39xL8Q@mail.gmail.com>
 <CABUevEzpjjCPjWzcs+L5CtcLPeCyVTECKP-LScu7tWfgUmnwPQ@mail.gmail.com>
 <CAMaW3VgM5J4ifSvCL+XZ2Z1hSfLV9368gZKYXH1NUQX5CV53Tw@mail.gmail.com>
In-Reply-To: 
 <CAMaW3VgM5J4ifSvCL+XZ2Z1hSfLV9368gZKYXH1NUQX5CV53Tw@mail.gmail.com>
From: Akshat Jaimini <destrex271@gmail.com>
Date: Fri, 5 Jan 2024 08:22:40 +0530
Message-ID: 
 <CAMaW3Vj-J5GgTmYN4Q_J48c92jEY0=5Wvnf1Rn2gWGRF6wA2sQ@mail.gmail.com>
Subject: Re: [INFO] Regarding bugs in Testing Harness
To: Magnus Hagander <magnus@hagander.net>
Cc: pgsql-www@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000b8126d060e29f11d"
Archived-At: 
 <https://www.postgresql.org/message-id/CAMaW3Vj-J5GgTmYN4Q_J48c92jEY0%3D5Wvnf1Rn2gWGRF6wA2sQ%40mail.gmail.com>
Precedence: bulk

--000000000000b8126d060e29f11d
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Migration Tests added to the harness.
Now it should report any such errors properly without failing silently.

Regards,
Akshat Jaimini

On Wed, 3 Jan, 2024, 12:32 Akshat Jaimini, <destrex271@gmail.com> wrote:

> Great! The harness is working properly now too.
> Thanks!
> I'll add another test to check the migration process too so that these
> problems are also notified automatically.
>
> Regards,
> Akshat Jaimini
>
> On Tue, Jan 2, 2024 at 11:09=E2=80=AFPM Magnus Hagander <magnus@hagander.=
net>
> wrote:
>
>> The whole table account_communityauthlastlogin is managed outside of
>> the django ORM, because django doesn't support proper primary keys
>> (see commit 9e70a4e0c32f8db0178f05dac4c1fca7b317e7c5).
>>
>> We don't have anything beyond this on the prod server, but it does
>> look like this is just a plain bug in the commit, which breaks it. And
>> the testing harness found it!
>>
>> Fix pushed in fbfe3cfc.
>>
>> //Magnus
>>
>>
>> On Tue, Jan 2, 2024 at 6:07=E2=80=AFPM Akshat Jaimini <destrex271@gmail.=
com>
>> wrote:
>> >
>> > Turns out the harness was not able to build the website locally in the
>> dev environment. This is due to the recent patch for 'making the foreign
>> key from last login table be ON DELETE CASCADE'. As far as I understood
>> from the commit message this needs to be handled by postgres instead of
>> Django. Have we implemented something on our production server which all=
ows
>> this? If yes then kindly share that so we can get the harness back up an=
d
>> running. Currently, it is unable to parse the file
>> 'pgweb/account/migrations/0004_cauth_last_login.py' while running
>> migrations.
>> >
>> > Regards,
>> > Akshat Jaimini
>> >
>> > On Tue, Jan 2, 2024 at 1:37=E2=80=AFPM Akshat Jaimini <destrex271@gmai=
l.com>
>> wrote:
>> >>
>> >> Hi,
>> >> This is to update that recently the accessibility tests of the testin=
g
>> harness are not working as intended. Currently looking into the possible
>> causes. This might take a few days to get back up and running; The
>> functionality tests are running for now.
>> >>
>> >> Regards,
>> >> Akshat Jaimini
>>
>

--000000000000b8126d060e29f11d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Migration Tests added to the harness.<div dir=3D"auto">No=
w it should report any such errors properly without failing silently.</div>=
<div dir=3D"auto"><br></div><div dir=3D"auto">Regards,</div><div dir=3D"aut=
o">Akshat Jaimini</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr=
" class=3D"gmail_attr">On Wed, 3 Jan, 2024, 12:32 Akshat Jaimini, &lt;<a hr=
ef=3D"mailto:destrex271@gmail.com">destrex271@gmail.com</a>&gt; wrote:<br><=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>Great! The harnes=
s is working properly now too. <br></div><div>Thanks!</div><div>I&#39;ll ad=
d another test to check the migration process too so that these problems ar=
e also notified automatically.<br></div><div><br></div><div>Regards,</div><=
div>Akshat Jaimini<br></div></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Tue, Jan 2, 2024 at 11:09=E2=80=AFPM Magnu=
s Hagander &lt;<a href=3D"mailto:magnus@hagander.net" target=3D"_blank" rel=
=3D"noreferrer">magnus@hagander.net</a>&gt; wrote:<br></div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex">The whole table account_communityauthlas=
tlogin is managed outside of<br>
the django ORM, because django doesn&#39;t support proper primary keys<br>
(see commit 9e70a4e0c32f8db0178f05dac4c1fca7b317e7c5).<br>
<br>
We don&#39;t have anything beyond this on the prod server, but it does<br>
look like this is just a plain bug in the commit, which breaks it. And<br>
the testing harness found it!<br>
<br>
Fix pushed in fbfe3cfc.<br>
<br>
//Magnus<br>
<br>
<br>
On Tue, Jan 2, 2024 at 6:07=E2=80=AFPM Akshat Jaimini &lt;<a href=3D"mailto=
:destrex271@gmail.com" target=3D"_blank" rel=3D"noreferrer">destrex271@gmai=
l.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Turns out the harness was not able to build the website locally in the=
 dev environment. This is due to the recent patch for &#39;making the forei=
gn key from last login table be ON DELETE CASCADE&#39;. As far as I underst=
ood from the commit message this needs to be handled by postgres instead of=
 Django. Have we implemented something on our production server which allow=
s this? If yes then kindly share that so we can get the harness back up and=
 running. Currently, it is unable to parse the file &#39;pgweb/account/migr=
ations/0004_cauth_last_login.py&#39; while running migrations.<br>
&gt;<br>
&gt; Regards,<br>
&gt; Akshat Jaimini<br>
&gt;<br>
&gt; On Tue, Jan 2, 2024 at 1:37=E2=80=AFPM Akshat Jaimini &lt;<a href=3D"m=
ailto:destrex271@gmail.com" target=3D"_blank" rel=3D"noreferrer">destrex271=
@gmail.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; Hi,<br>
&gt;&gt; This is to update that recently the accessibility tests of the tes=
ting harness are not working as intended. Currently looking into the possib=
le causes. This might take a few days to get back up and running; The funct=
ionality tests are running for now.<br>
&gt;&gt;<br>
&gt;&gt; Regards,<br>
&gt;&gt; Akshat Jaimini<br>
</blockquote></div>
</blockquote></div>

--000000000000b8126d060e29f11d--