public inbox for [email protected]  

help / color / mirror / Atom feed

From: Akshat Jaimini <[email protected]>
To: Magnus Hagander <[email protected]>
Cc: [email protected]
Subject: Re: [INFO] Regarding bugs in Testing Harness
Date: Wed, 3 Jan 2024 12:32:58 +0530
Message-ID: <CAMaW3VgM5J4ifSvCL+XZ2Z1hSfLV9368gZKYXH1NUQX5CV53Tw@mail.gmail.com> (raw)
In-Reply-To: <CABUevEzpjjCPjWzcs+L5CtcLPeCyVTECKP-LScu7tWfgUmnwPQ@mail.gmail.com>
References: <CAMaW3VgbJmp8BQw_QUshk4JfFhOco--ymhEwjwGRTvftzqpiZg@mail.gmail.com>
	<CAMaW3ViEK3=hkR9bEeaHoNFfos5s_xnNMqdXZUGVqL_k39xL8Q@mail.gmail.com>
	<CABUevEzpjjCPjWzcs+L5CtcLPeCyVTECKP-LScu7tWfgUmnwPQ@mail.gmail.com>

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 PM Magnus Hagander <[email protected]> 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 PM Akshat Jaimini <[email protected]>
> 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 allows
> 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
> 'pgweb/account/migrations/0004_cauth_last_login.py' while running
> migrations.
> >
> > Regards,
> > Akshat Jaimini
> >
> > On Tue, Jan 2, 2024 at 1:37 PM Akshat Jaimini <[email protected]>
> wrote:
> >>
> >> Hi,
> >> This is to update that recently the accessibility tests of the testing
> 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
>

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: [INFO] Regarding bugs in Testing Harness
  In-Reply-To: <CAMaW3VgM5J4ifSvCL+XZ2Z1hSfLV9368gZKYXH1NUQX5CV53Tw@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox