qa-devel December 2013

qa-devel@lists.fedoraproject.org

5 participants
29 discussions

[Fedora QA] #436: SSH access to systems in Beaker lab
by fedora-badges 20 Apr '16

20 Apr '16

#436: SSH access to systems in Beaker lab --------------------------------------+--------------------- Reporter: atodorov | Owner: tflink Type: defect | Status: new Priority: major | Milestone: Component: Blocker bug tracker page | Version: Keywords: | Blocked By: Blocking: | --------------------------------------+--------------------- = bug description = Currently systems in Beaker lab can be accessed only through bastion.fp.o which is not as convenient as direct SSH into the system. There's also the question whether or not to open the systems directly to the Internet. This needs to be discussed with infra. Filing here so it doesn't get lost. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/436> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 4

[Fedora QA] #437: Need to import daily Fedora snapshots into Beaker
by fedora-badges 29 Jan '15

29 Jan '15

#437: Need to import daily Fedora snapshots into Beaker --------------------------------------+--------------------- Reporter: atodorov | Owner: tflink Type: task | Status: new Priority: major | Milestone: Component: Blocker bug tracker page | Version: Keywords: | Blocked By: Blocking: | --------------------------------------+--------------------- = bug description = In order to perform any meaningfull testing Beaker needs to import more recent Fedora trees. It could be daily(nightly) snapshots or less often depending on available resources. The tree directory structure needs to be a copy/snapshot of the current state at the time of import. The reason is b/c devel trees utilize one URL but the contents under this URL are updated in a rolling fashion. We need tree URLs where content is not changing in order to produce consistent test results. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/437> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 1

[Fedora QA] #433: blocker proposal form forgets everything after login timeout
by fedora-badges 20 Jan '15

20 Jan '15

#433: blocker proposal form forgets everything after login timeout --------------------------------------+--------------------- Reporter: kvolny | Owner: tflink Type: defect | Status: new Priority: major | Milestone: Component: Blocker bug tracker page | Version: Keywords: | Blocked By: Blocking: | --------------------------------------+--------------------- = bug description = I was trying to propose a F20 blocker. I needed to gather information from multiple bugs, so it took me longer to write the justification. After finishing and submitting that, I was presented with a login screen. After logging in again, I was redirected to the proposal form again, but it was completely empty, all the text that took me so long to write was gone. (Okay, I'm a smart guy and I had it in clipboard for such case, but if I had forgotten ... booh.) = bug analysis = Seems the login code doesn't care about other variables in the http request ... = fix recommendation = 1) If there is such a short login timeout, the user should be warned about it (e.g. countdown timer on the page) and the page should allow refresh without submitting the data. 2) Once the login expires, the submitted data should be caried over all the redirects back to the submission form. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/433> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 2

Review Request 37: Fix sequences in alembic
by Martin Krizek 21 Feb '14

21 Feb '14

----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviewboard-tflink.rhcloud.com/r/37/ ----------------------------------------------------------- Review request for blockerbugs. Repository: blockerbugs Description ------- commit abf5fe2abbcfbce45d103864f5ba40fc89f233fa Author: Martin Krizek <mkrizek(a)redhat.com> Date: Tue Jul 16 13:57:28 2013 +0200 Fix sequences in alembic Sequences need to be created separately. The patch also fixes a few typos. https://bitbucket.org/zzzeek/alembic/issue/73/more-pg-nextval-it-needs-the-… Diffs ----- alembic/versions/487cb8ccce92_dropping_flask_login.py e64dacb2e3b1a3d14bf38e1116df183ded9793d9 alembic/versions/1d12b74d12bd_add_userinfo_table.py 86dc390ed5e49b0a3ca058e163bc02b070d3d294 Diff: http://reviewboard-tflink.rhcloud.com/r/37/diff/ Testing ------- Thanks, Martin Krizek

1 4

Review Request 62: Fix needinfo field length
by Martin Krizek 21 Feb '14

21 Feb '14

----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviewboard-tflink.rhcloud.com/r/62/ ----------------------------------------------------------- Review request for blockerbugs. Repository: blockerbugs Description ------- Now that we support multiple needinfo flags, we also need to increase length of the needinfo field. Diffs ----- blockerbugs/models/bug.py 695d0ce3ca800ad8cd8d8324bc01726a84eade1b alembic/versions/1dfd879c7637_fix_needinfo_field_l.py PRE-CREATION Diff: http://reviewboard-tflink.rhcloud.com/r/62/diff/ Testing ------- Testing done on my dev machine. Thanks, Martin Krizek

1 1

Review Request 61: Rename line.png to line-bottom.png
by Martin Krizek 21 Feb '14

21 Feb '14

----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviewboard-tflink.rhcloud.com/r/61/ ----------------------------------------------------------- Review request for blockerbugs. Repository: blockerbugs Description ------- It appears that we've been getting ""GET /static/img/line-bottom.png HTTP/1.1" 404" for quite some time now... commit fb18e118d108a8965a2ea8a2087bf1baa88cc193 Author: Martin Krizek <mkrizek(a)redhat.com> Date: Tue Dec 17 10:47:34 2013 +0100 Rename line.png to line-bottom.png to reflect the actual state of css. Diffs ----- blockerbugs/static/img/line.png 6c111c3c3ed2118dfe803e02a6b0c8245010082a blockerbugs/static/img/line-bottom.png PRE-CREATION Diff: http://reviewboard-tflink.rhcloud.com/r/61/diff/ Testing ------- Thanks, Martin Krizek

1 1

Review Request 60: Insufficient logging for bug proposal form issues
by Martin Krizek 21 Feb '14

21 Feb '14

----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviewboard-tflink.rhcloud.com/r/60/ ----------------------------------------------------------- Review request for blockerbugs. Repository: blockerbugs Description ------- Errors were logged with level 'debug' which caused them to not being logged at all on prod. commit cb8169121c4c27ef8893eef11b8b0b0ef7f1dea7 Author: Martin Krizek <mkrizek(a)redhat.com> Date: Tue Dec 17 15:11:26 2013 +0100 Set log level to 'error' for errors in the blocker proposal form Fixes: T24 Diffs ----- blockerbugs/templates/propose_bug.html 848a3e2bd7b94780348a107230f057801c7ea868 blockerbugs/controllers/main.py 5455e1aa2bbf6edc551223ee6fccb9c6236f0eb8 Diff: http://reviewboard-tflink.rhcloud.com/r/60/diff/ Testing ------- Thanks, Martin Krizek

1 1

[Maniphest] [Created] T24: Insufficient logging for bug proposal form issues
by tflink (Tim Flink) 15 Jan '14

15 Jan '14

tflink created this task. tflink added a subscriber: tflink. tflink added a project: blockerbugs TASK DESCRIPTION I got a report of a failed proposal today where the form said there were errors but everything looks fine and no details were provided. There is currently no logging of form errors in the app, and that would have been useful in this case. If there's one report, I suspect that there have been other form validation failures which have gone unreported. Attached to this bug is screenshot of what the user reported {F10} TASK DETAIL https://phab.qadevel.cloud.fedoraproject.org/T24 To: tflink Cc: qa-devel, tflink

1 3

RFC: Taskotron task description format
by Tim Flink 15 Jan '14

15 Jan '14

I've been working on this for a bit but finally have enough together that we can start talking about the task description format for taskotron. The code to actually run tasks (well, task. for now, rpmlint is all that's supported) is up at: https://bitbucket.org/fedoraqa/libtaskotron-demo The runner code isn't very good yet but I didn't want to wait until it was done before starting to discuss the task description format. Continuing the use of rpmlint as an example, I have a task repository set up on bitbucket: https://bitbucket.org/fedoraqa/task-rpmlint At the moment, that task yaml file for rpmlint [1] looks like: dependencies: - rpmlint - libtaskbot input: args: envr,arch preparation: koji: download $envr execution: python: run_rpmlint.py $workdir post: shell: clean $workdir report: resultdb: something [1]https://bitbucket.org/fedoraqa/task-rpmlint/src/be90c723a11f3cec3a7ee72e3… In a nutshell, the idea is to keep repetitive code out of the tasks without requiring everything to be written in the same language or porting the library to any language people want to use (perl, c, bash etc.). The execution of the task is described in the yml file and eventually delegates actual execution to the python file described in that yml file. Output, for now, is in TAP format. The runner just spits it out as text for the moment but eventually, that TAP output will be used for reporting the results. Items prepended with '$' represent variables - either things determined at runtime (the working directory) or things that are arguments to the specific task run (the envr of packages to check). Examples of what future features could look like: execution: beaker: job=somejob.xml distro=$latestfedora preparation: bodhi: download $updates preparation: openstack: image=imagename config=someconfigtype size=m1.small execution: infinity: config=test/sometest.cfg Any thoughts on whether this direction is a good direction to take or suggestions on how the format could be improved? Eventually, I want to send this out to devel@ for input but figured that the smaller group of folks here would be a good start. Thanks, Tim

4 6

[Maniphest] [Created] T21: Do not display obsolete and deleted updates
by tflink (Tim Flink) 14 Jan '14

14 Jan '14

mkrizek created this task. mkrizek claimed this task. mkrizek added a subscriber: mkrizek. mkrizek added a project: blockerbugs TASK DESCRIPTION Currently, the app knows of no way how to deal with updates that were deleted from bodhi. This results in displaying deleted update as a potential fix for a bug. Also, the app display an obsolete update as a potential fix which it shouldn't. The update sync code should go through the updates stored in the app's db and somehow mark those that were no longer present in bodhi or that have status 'obsolete' as 'do not display'. TASK DETAIL https://phab.qadevel.cloud.fedoraproject.org/T21 To: mkrizek Cc: qa-devel, mkrizek

1 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

qa-devel December 2013