Rob Percival

We now have a Terraform config for deploying Trillian to GCP with a Cloud Spanner database. However, it's still necessary to use the shell scripts if you want to use...

After seeing a similar timeout occur after reducing the max number of connections to the MySQL server (in PR #722), I tried increasing the max_connections MySQL server parameter from the...

The cause of this was a bug in PR #734 that resulted in sequencing passes failing, but the integration test not reporting this as an error. Instead, it would just...

Yes, [the LogOperationManager swallows sequencing errors](https://github.com/google/trillian/blob/master/server/log_operation_manager.go#L344) and so the integration tests can't detect that there's a problem - they just run until the timeout. There's a relevant TODO here: https://github.com/google/trillian/blob/master/server/log_operation_manager.go#L378

[The LogOperationManager still swallows these errors](https://github.com/google/trillian/blob/master/server/log_operation_manager.go#L408).

The TODO is now here: https://github.com/google/trillian/blob/c53ded5073f260f9a9198c47064ff13355f6ef72/server/log_operation_manager.go#L285

As mentioned in the OP, this is probably a result of running tests in parallel. Some test suites, e.g. for Django, will create a database during setup. When you only...

Here's another example of that license format that is incorrectly classified: https://github.com/jmespath/go-jmespath/blob/c2b33e8439af944379acbdd9c3a5fe0bc44bd8a5/LICENSE

@jezdez, could the workflow get an approval please?

Seems to have passed the test suite (the failing tests seem to be caused by something else).