1
78%
master: 76%

Ran 25 Jun 2019 06:39AM UTC

Files 290

Run time 15s

Badge

Embed ▾

Committed 25 Jun 2019 06:28AM UTC coverage: 77.382% (+0.006%) from 77.376%

Job # 4766.1

Build Type

Pull #1092

travis-ci

Committed by

web-flow

Commit Message

Flows were stuck in running for RPA Activities if on production environments (Faster environments).
This was happening due to the order of execution steps. First the message/execution was produced on queue, and then it was paused.
This triggered a race condition in which if there was some sort of check on the execution between putting the message on the queue and pausing the execution, a null pointer was thrown.
What was done: reverted the order (pause -> execute), removed the set pause status from other places, changed how the doAction method works in Cloudslang such that the runEnvironment is fully populated before pausing (and persisting) the execution.
Also fixed another defect that made the Multi Instance with one lane having RPA activities fail because the branchId was mistakenly removed from the RpaExecutionMessage

Signed-off-by: platon <flavius-rares.platon@microfocus.com>

Pull Request Pull Request #1092: Flows were stuck in running for RPA Activities

Run Details

6148 of 7945 relevant lines covered (77.38%)

107.14 hits per line

CloudSlang / cloud-slang / 4766 / 1
78%
master: 76%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 4766.1

CloudSlang / cloud-slang / 4766 / 1 78% master: 76%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 4766.1

CloudSlang / cloud-slang / 4766 / 1
78%
master: 76%

README BADGES
x