Tails

#2 Updated by Anonymous 2017-04-27 09:58:27

• Assignee set to sajolida
• QA Check set to Info Needed

The note you are linking to in the description does not exist. May you please clarify what this is about?
Thanks! Please reassign to me afterwards.

#3 Updated by sajolida 2017-04-28 12:41:04

• Description updated
• Assignee deleted (sajolida)
• QA Check deleted (Info Needed)

I fixed the description. It should be Feature #12134#note-7. It seems to me that the corresponding fix in the test suite is 1320ee5fe7, which we might be able to actually do ourselves when changing the title of /home. If this works for anonym, than that would be another option…

#4 Updated by Anonymous 2018-01-23 10:10:53

• Parent task changed from Feature #12035 to Feature #14877

We did not work on this for 2017’s donation campaign, adding this to the todo list of next year.

#5 Updated by sajolida 2018-08-31 18:23:40

• Category set to Fundraising
• Assignee set to sajolida
• Target version set to Tails_3.10.1

#6 Updated by sajolida 2018-09-18 22:13:42

• QA Check set to Ready for QA
• Feature Branch set to web/12156-constant-title-on-home

I have a branch that works around that with a bit of JavaScript :)

I’ll monitor Jenkins to make sure I’m not breaking the test suite before assigning this to review to somebody.

#7 Updated by sajolida 2018-09-21 20:46:53

• Status changed from Confirmed to In Progress

Applied in changeset commit:cf6711fc43ad1ffc467383f1f22ca4861d390b0f.

#8 Updated by sajolida 2018-09-21 21:12:54

• Assignee changed from sajolida to intrigeri

Trying to read the output of the test suite for the first time:

1. It seems like the failures I have on test_Tails_ISO_web-12156-constant-title-on-home are unrelated to my changes:

cucumber features/apt.feature:14 # Scenario: Install packages using apt
cucumber features/emergency_shutdown.feature:13 # Scenario: Tails erases memory on DVD boot medium removal: aufs read-write branch
cucumber features/additional_software_packages.feature:8 # Scenario: Additional software packages are installed even without network

2. But I can’t find anything releveant when searching for “Tails homepage” in the debug.log so I’m not sure either that it passes…

intrigeri: Do you mind having a look?

#9 Updated by intrigeri 2018-09-28 09:19:39

• Assignee changed from intrigeri to sajolida
• % Done changed from 0 to 10
• QA Check deleted (Ready for QA)

Two hints:

• I think all the affected scenarios are tagged fragile so they won’t run on Jenkins by default. To force them to run, add the +force-all-tests suffix to the name of your branch.
• I think you need to look for “startup page” and not “Tails homepage”: the latter is https://tails.boum.org/ (which is not relevant here) while the former is /home (that’s what you want).

#12 Updated by sajolida 2018-10-09 23:07:07

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

Meta: I’m happy to play with the test suite like that (without clocking everything) and learn more about how our CI is working. But maybe it’s not the most productive us of our time :) I’ll let you tell me.

So the build of the tests started and failed:

https://jenkins.tails.boum.org/job/test_Tails_ISO_web-12156-constant-title-on-home-force-all-tests/lastFailedBuild/console

The reason I understand is that it was not able to copy the ISO from the build of the image:

Unable to find a build for artifact copy from: build_Tails_ISO_web-12156-constant-title-on-home-force-all-tests

While the build of the image is successful, earlier in date, and with the same commit:

https://jenkins.tails.boum.org/job/build_Tails_ISO_web-12156-constant-title-on-home-force-all-tests/1/

How is that?

#13 Updated by intrigeri 2018-10-10 13:56:07

• Assignee changed from intrigeri to sajolida
• QA Check changed from Info Needed to Dev Needed

> Meta: I’m happy to play with the test suite like that (without clocking everything) and learn more about how our CI is working. But maybe it’s not the most productive us of our time :) I’ll let you tell me.

Meta: I’m very happy you’re willing to learn more about our CI. Now, until we have someone with the skills & budget to turn your feedback into actual improvements, don’t expect too much. So feel free to learn just enough for you to make good use of the current state of things and to report issues: whatever list of issues we come up with will be useful when it’s time to take a step back and decide what’s the best way forward :)

> So the build of the tests started and failed:
> https://jenkins.tails.boum.org/job/test_Tails_ISO_web-12156-constant-title-on-home-force-all-tests/lastFailedBuild/console

FYI links with “lastFailedBuild” are not stable. In this case, https://jenkins.tails.boum.org/job/test_Tails_ISO_web-12156-constant-title-on-home-force-all-tests/1/console is the stable link to that run.

> The reason I understand is that it was not able to copy the ISO from the build of the image:

>

> Unable to find a build for artifact copy from: build_Tails_ISO_web-12156-constant-title-on-home-force-all-tests
> 

Right. It looks like you’ve manually triggered this test suite run. Correct?
I guess you did that because the test suite had not run after the ISO was built yesterday afternoon UTC. I think that’s because our on-call sysadmin rebooted systems around that time.

Unfortunately, triggering test suite runs manually does not work: with the current design/implementation of our CI, any test suite run must be triggered by an ISO build and will inherit its “artifacts” (i.e. ISO image). Jobs 2 and 3 (that are currently running) don’t expose this problem and should give you the info you’re looking for :)

#15 Updated by sajolida 2018-10-12 02:07:41

• Assignee changed from sajolida to intrigeri
• QA Check changed from Dev Needed to Info Needed

I got the same error on build #5 with my updated commit. Now I don’t know what to do…

Note that we won’t block on this to launch the donation campaign, so let’s take it easy.

#17 Updated by intrigeri 2018-10-12 14:09:35

• % Done changed from 10 to 80
• QA Check changed from Info Needed to Ready for QA

intrigeri wrote:
> So I’m going to do an extra careful review + test and if happy, merge this into master → stable → devel.

Done! I’ll check the next test suite run on a branch that has +force-all-tests, to ensure this did not break anything.

#18 Updated by intrigeri 2018-10-12 19:53:40

• Status changed from In Progress to Resolved
• Assignee deleted (intrigeri)
• % Done changed from 80 to 100
• QA Check changed from Ready for QA to Pass

The only failure on https://jenkins.tails.boum.org/view/Tails_ISO/job/test_Tails_ISO_feature-15936-linux-4.18-stable-bump-debian-force-all-tests/4/ is unrelated. Congrats for your first contribution to our test suite :)