Bug #10337
isotester1 is not running the test suite from the correct branch
100%
Description
isotester1 doesn’t run the test suite with the intended commit checked out. Specifically, from the console logs, the COMMIT=a3f6635 seems wrong — that commit is in devel => we are not testing the branches of Feature #6094 and Feature #9516.
Also see Bug #10288#note-5 for some details on what this means for the “metrics” purposes of isotester1.
Subtasks
History
#1 Updated by anonym 2015-10-05 13:50:03
- blocks #8668 added
#2 Updated by intrigeri 2015-10-05 13:53:32
Pushed a commit that might fix it, but perhaps I missed other needed bits.
#3 Updated by anonym 2015-10-05 14:03:23
- Description updated
#4 Updated by bertagaz 2015-10-06 01:49:11
- Assignee changed from bertagaz to anonym
- % Done changed from 0 to 50
- QA Check set to Ready for QA
O_o
Sorry for the mess, don’t know how it happened, maybe I didn’t double check, or was too exhausted.
I’ve just updated the job, it now runs against commit 2f2dde6 since build 28
If that sounds ok to you, please close this ticket.
#5 Updated by anonym 2015-10-06 01:54:49
- Status changed from Confirmed to Resolved
- Assignee deleted (
anonym) - % Done changed from 50 to 100
- QA Check changed from Ready for QA to Pass
bertagaz wrote:
> O_o
>
> Sorry for the mess, don’t know how it happened, maybe I didn’t double check, or was too exhausted.
>
> I’ve just updated the job, it now runs against commit 2f2dde6 since build 28
>
> If that sounds ok to you, please close this ticket.
It does, and all looks good: now I see that COMMIT=2f2dde6 (which is the tip of experimental) and:
00:05:06.435 Given Tails has booted from DVD and logged in with an administration password and the network is connected # features/step_definitions/snapshots.rb:174
which is what I’d expect. Yay! Let’s just freeze at that commit so we don’t get inconsistencies for ISO vs test suite.
#6 Updated by intrigeri 2015-11-06 09:35:07
- Deliverable for set to 267