-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
roachtest: hibernate failed #34693
Comments
SHA: https://github.com/cockroachdb/cockroach/commits/4e2e450ecf5c3f73c7de46e48696528468803db7 Parameters: To repro, try:
Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=1128035&tab=buildLog
|
The second failures seem to be predominantly:
|
I'm going to spend some time looking into this today. Clearly something
has changed and not for the better.
…On Thu, Feb 7, 2019, 10:15 Alfonso Subiotto Marqués < ***@***.*** wrote:
The second failures seem to be predominantly:
org.hibernate.test.resulttransformer.ResultTransformerTest > classMethod FAILED
org.hibernate.testing.junit4.CallbackException
Caused by: org.hibernate.service.spi.ServiceException
Caused by: org.hibernate.exception.JDBCConnectionException
Caused by: org.postgresql.util.PSQLException
Caused by: java.net.ConnectException
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#34693 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABihueCFR92SuZ9-64MQ7AWBt8LYCSkEks5vLEMFgaJpZM4amjHp>
.
|
From the logs, it looks like this crashed the node: SELECT
count(*) AS col_0_0_
FROM
human AS human0_
INNER JOIN mammal AS human0_1_ ON human0_.mammal = human0_1_.animal
INNER JOIN animal AS human0_2_ ON human0_.mammal = human0_2_.id
CROSS JOIN human_family AS family1_,
human AS human2_
INNER JOIN mammal AS human2_1_ ON human2_.mammal = human2_1_.animal
INNER JOIN animal AS human2_2_ ON human2_.mammal = human2_2_.id
WHERE
(human0_.mammal = family1_.human1 AND family1_.human2 = human2_.mammal)
AND (
SELECT
family1_.human2
FROM
human_family AS family1_,
human AS human2_
INNER JOIN mammal AS human2_1_ ON human2_.mammal = human2_1_.animal
INNER JOIN animal AS human2_2_ ON human2_.mammal = human2_2_.id
WHERE
human0_.mammal = family1_.human1 AND family1_.human2 = human2_.mammal
)
= $1; |
SHA: https://github.com/cockroachdb/cockroach/commits/4bdf0ad7b3190e1836e311d2b05478e8cda0bfe6 Parameters: To repro, try:
Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=1129727&tab=buildLog
|
SHA: https://github.com/cockroachdb/cockroach/commits/e4127466ae0a44efb624afcaf0861903028b6e18 Parameters: To repro, try:
Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=1129825&tab=buildLog
|
SHA: https://github.com/cockroachdb/cockroach/commits/70cd0458348655fb74f4e2cb89aa202b5dd89ed0 Parameters: To repro, try:
Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=1129807&tab=buildLog
|
The 2.1 failure worries me. It doesn't seem to be related to the sql panic. I'm going to spend monday getting to the bottom of both. |
SHA: https://github.com/cockroachdb/cockroach/commits/40e403544d60b1a44b8b1ed961a817c77d67aa31 Parameters: To repro, try:
Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=1131411&tab=buildLog
|
SHA: https://github.com/cockroachdb/cockroach/commits/b80d241d5693d6ba2bde01ae9167b49b04b47226 Parameters: To repro, try:
Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=1133193&tab=buildLog
|
So I've investigated the 2.1 failure and it was a transient failure. |
SHA: https://github.com/cockroachdb/cockroach/commits/10f8010fa5778e740c057905e2d7664b5fd5d647 Parameters: To repro, try:
Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=1135549&tab=buildLog
|
Fixed via #34795. |
SHA: https://github.com/cockroachdb/cockroach/commits/66f13c1d9a12c31e18a198da4ff5ac0bbe2db781
Parameters:
To repro, try:
Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=1127849&tab=buildLog
The text was updated successfully, but these errors were encountered: