-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[0.5.0] Several mimetype-related tests are failing #634
Comments
Output on a fresh
|
I have also observed these errors locally, however after running the updater (unclear and unlikely that had an impact) and shutting down all the workstation VMs, most tests were once again passing on the branch in 632. It seems like the issue is the DispVM templates which weren't shutdown after the initial provisioning run: We should check the shutdown order within the GUI updater, and since a normal user would have to run through an updater cycle to get their workstation in order after running the manual --apply command, this could address the situation in non-dev scenarios, but would obvious be an issue for dev |
Thanks @emkll, that's helpful. A full host reboot likely would have straightened me out, I'll confirm that today. |
Encountered again on 0.5.0-rc3 as part of QA for fresh install. Ran the updater, then manually restarted the VMs, and all tests were passing. Running make-dev and make-test from the same code, via the main branch, showed all tests passing immediately, so I suspect the state drift is related to our use of the |
Related to freedomofpress/securedrop-updater#35 |
Closing, it seems like freedomofpress/securedrop-updater#35 is the underlying issue here, and 0.5.0 has been released. |
FWIW I'm no longer able to reproduce these test failures. On latest main. i.e. 6b4896d, I'm seeing 100% of tests passing. freedomofpress/securedrop-updater#35 should still be addressed, but at least our tests are passing again. |
Last tested on PR #632 (which will likely become 0.5.0-rc3).
failing tests output
Let's make sure to get these down to zero prior to releasing 0.5.0 final.
The text was updated successfully, but these errors were encountered: