Bug #12528

Cucumber test reports sometimes cannot be viewed on Jenkins: Gateway Time-out

Added by intrigeri 2017-05-10 11:31:14 . Updated 2017-07-05 08:37:00 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Continuous Integration
Target version:
Tails_3.1
Start date:
2017-05-10
Due date:
% Done:

100%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

e.g. https://jenkins.tails.boum.org/view/RM/job/test_Tails_ISO_feature-stretch/lastFailedBuild/cucumberTestReport/

What recent change can possibly have broken this?

Subtasks

Related issues

Blocks Tails - Feature #13233: Core work 2017Q3: Sysadmin (Maintain our already existing services) Resolved 2017-06-29

History

#1 Updated by bertagaz 2017-05-11 15:04:08

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 10

intrigeri wrote:
> e.g. https://jenkins.tails.boum.org/view/RM/job/test_Tails_ISO_feature-stretch/lastFailedBuild/cucumberTestReport/
>
> What recent change can possibly have broken this?

I don’t see one, apart maybe some package upgrade that happened lately. But after some tests, it seems that when trying to load a cucumber report, the CPU gets used at 99% for some time and the memory gets short, then the 504 error appears. But when I try to load the same page later, it sometimes works. I’ll dig a bit more and maybe will try to add a bit more memory to the VM.

#2 Updated by intrigeri 2017-05-18 12:14:43

I’ve seen this happen with CPU congestion but memory state being OK:

              total        used        free      shared  buff/cache   available
Mem:           2650         902          80          80        1666        1522
Swap:             0           0           0

So I would first try giving the VM a second vCPU, and leaving memory settings unchanged.

#3 Updated by intrigeri 2017-05-18 12:14:52

  • Subject changed from Cucumber test reports cannot be viewed on Jenkins: Gateway Time-out to Cucumber test reports sometimes cannot be viewed on Jenkins: Gateway Time-out

#4 Updated by bertagaz 2017-05-21 12:24:52

  • % Done changed from 10 to 30

intrigeri wrote:
> So I would first try giving the VM a second vCPU, and leaving memory settings unchanged.

Done. Seems indeed to work a bit better, even if the 504 error sometimes still happens. Seems it does so when the script that update the jobs list is running, and git is cloning the repo. Let test the change a bit more to see if it’s enough.

#5 Updated by bertagaz 2017-05-21 16:03:11

  • Target version changed from Tails_3.0~rc1 to Tails_3.0

#6 Updated by intrigeri 2017-05-22 06:57:02

  • Priority changed from Elevated to Normal

(This problem happens much less often than I thought initially.)

#7 Updated by intrigeri 2017-05-27 08:45:14

  • Target version changed from Tails_3.0 to Tails_3.1

It can wait one more month => cleaning up a bit your 3.0 plate :)

#8 Updated by intrigeri 2017-06-05 10:29:32

See email I’ve just sent to -sysadmins@.

#9 Updated by intrigeri 2017-06-29 10:16:30

  • blocks Feature #13233: Core work 2017Q3: Sysadmin (Maintain our already existing services) added

#10 Updated by bertagaz 2017-07-05 08:32:00

  • Assignee changed from bertagaz to intrigeri
  • QA Check set to Info Needed

While starting Feature #12289, I’ve had a look at a bunch of cucumber reports and didn’t see this error again. Do you?

#11 Updated by intrigeri 2017-07-05 08:37:00

  • Status changed from In Progress to Resolved
  • Assignee deleted (intrigeri)
  • % Done changed from 30 to 100
  • QA Check changed from Info Needed to Pass

No, I’ve not seen this happen recently.