This repository was archived by the owner on Mar 24, 2026. It is now read-only.
Conversation
Member
Author
|
@knewmanTE The reason it was working on one machine and not the other was just variability in how fast the table populated on that machine. When reproducing the problem the "Fortunes" table would have between 0 and 4 rows on my vm. |
Member
Author
|
fyi this is a travis run of nodejs from my work. This includes the postgres changes made here as well as travis installing client and database via the scripts we use. It's still a work in progress for a few things but postgresql is fixed: https://travis-ci.org/nbrady-techempower/FrameworkBenchmarks/jobs/160604384 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR fixes a problem where the postgresql service was being killed during the database installation step before the "Fortunes" table was fully populated. It also removes precise support and other fixes that now make it travis compatible for the upcoming round-14 travis update.