1
0%
master: 0%

Ran 29 May 2016 12:22AM UTC

Files 15

Run time 1s

Badge

Embed ▾

Committed 28 May 2016 11:58PM UTC coverage: 82.108% (-0.06%) from 82.165%

Job # 1755.1

Build Type

Pull #530

travis-ci

Committed by

LAlbertalli

Commit Message

Added an additional fix for a similar error in #529

Background:
- When an object is modified by SQLAlchemy, it is invalidated so need to be fetched again from the DB
- If there's an exception during a transaction, SQLAlchemy performs a rollback and mark the connection as dirty.

Bug:
- When handling exceptions, the exception handler tries to access the name of the cluster in the main object. Since the name has been invalidated due to a write, SQLAlchemy tries to fetch it on a 'dirty' connection and spits out an error. Solution:
- Fetch the information for handling the exception before starting the process.

Pull Request Pull Request #530: Fix529 1

Run Details

2345 of 2856 relevant lines covered (82.11%)

0.82 hits per line

Source Files on job 1755.1

Coverage	∆	File	Lines	Relevant	Covered	Missed	Hits/Line

airbnb / superset / 1755 / 1
0%
master: 0%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1755.1

airbnb / superset / 1755 / 1 0% master: 0%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1755.1

airbnb / superset / 1755 / 1
0%
master: 0%

README BADGES
x