-
Notifications
You must be signed in to change notification settings - Fork 160
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
Migrate db tests away from goconvey #2986
Labels
Comments
lukedirtwalker
added a commit
that referenced
this issue
Aug 13, 2019
Remove goconvey from -pathdb -periodic -util tests. Without convey we have better insights into failures that happen in CI. Contributes #2986
lukedirtwalker
added a commit
to lukedirtwalker/scion
that referenced
this issue
Aug 21, 2019
beacondb test suite beacondb/sqlite pathdb/sqlite part of scion-pki Contributes scionproto#2986
lukedirtwalker
added a commit
to lukedirtwalker/scion
that referenced
this issue
Aug 21, 2019
beacondb test suite beacondb/sqlite pathdb/sqlite part of scion-pki Contributes scionproto#2986
lukedirtwalker
added a commit
to lukedirtwalker/scion
that referenced
this issue
Aug 21, 2019
beacondb test suite beacondb/sqlite pathdb/sqlite part of scion-pki Contributes scionproto#2986
lukedirtwalker
added a commit
that referenced
this issue
Aug 21, 2019
beacondb test suite beacondb/sqlite pathdb/sqlite part of scion-pki Contributes #2986
As I understand it, there's only |
scrye
added
i/good first issue
Good for newcomers
i/help wanted
Nobody is working on this at the moment
and removed
i/good first issue
Good for newcomers
i/help wanted
Nobody is working on this at the moment
labels
May 4, 2020
None of the db tests use goconvey anymore. Keeping the more generic issue #3016 open seems sufficient to keep track of removing the remaining occurrences. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
path, trust, and beacon db should no longer use goconvey. With it the output from CI is not detailed enough to properly analyze why a test failed.
We generally want to migrate away from goconvey, to standard go tests with assert libs.
The text was updated successfully, but these errors were encountered: