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.
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.
