jskladan (Josef Skládanka)Administrator
User

Projects (6)

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Tuesday

  • Clear sailing ahead.

User Details

User Since
Nov 7 2013, 8:47 AM (193 w, 2 d)
Roles
Administrator
Availability
Available

Recent Activity

Mon, Jul 17

jskladan edited the content of 20170717-fedoraqadevel.
Mon, Jul 17, 1:55 PM

Fri, Jul 14

jskladan accepted D1221: remove dnf cache support.

Macro devops: much changes very concerning

Fri, Jul 14, 12:54 PM

Wed, Jul 12

jskladan accepted D1220: rpm_utils: remove is_installed().
Wed, Jul 12, 2:03 PM

Tue, Jul 11

jskladan accepted D1219: taskotron-client: replace vars in yumrepoinfo.conf.

This is fine. At least before we have a better solution - I'd go with diff applied on top of the yumrepoinfo downloaded from repos, or installed from package, so we don't even need to keep the local copy, which can get outdated, and still not fail the checks.

Tue, Jul 11, 11:38 AM · infrastructure
jskladan added a comment to D1218: add SKIPPED outcome.

Well, I'm not fundamentally absolutely against it, but I'd be happier with you using INFO (which is already present) with "test was skipped" in note - especially if you say that it's supposed to be a pass anyway.
The intended semantics of the result values is
PASSED - everything ok, no questions asked
INFO - the same as PASSED for automation purposes, but a yellow flag for human consumers
NEEDS_INSPECTION - treated as FAILED in automation, red flag for human consumers
FAILED - something really went sideways

Tue, Jul 11, 11:26 AM

Fri, Jun 30

jskladan added a comment to T960: publish ResultsDB package to PyPI.

for future ref, the reasonable way to get around syncing requirements.txt and setup.py is adding:

+ with open('requirements.txt') as fd:
+     install_requires = [l.strip() for l in fd.readlines() if l.strip() and not l.strip().startswith('#>
...
+       install_requires=install_requires,

to setup.py

Fri, Jun 30, 2:33 PM · resultsdb
jskladan lowered the priority of T960: publish ResultsDB package to PyPI from "Low" to "Wishlist".

@mjia BTW what exactly is your use-case, and why is installing from repos not OK for you? I'm asking for two reasons

  1. packaging resultsdb for PyPi is proving to be rather a PITA
  2. if you actually need to use resultsdb, setup is necessary - like creating the database, for example - since you are going to need to solve this too (probably are right now anyway) is installing from repos (aka another line in that script that you'll have to have to setup resultsdb anyway) a problem?
Fri, Jun 30, 2:26 PM · resultsdb
jskladan raised the priority of T960: publish ResultsDB package to PyPI from "Wishlist" to "Low".

Hi, @mija, I don't have any fundamental issues with it, apart of the fact that it adds yet another place to store/track deps.

Fri, Jun 30, 1:35 PM · resultsdb
jskladan accepted D1217: requirements: limit Flask-RESTful to <= 0.3.5.
Fri, Jun 30, 1:05 PM
jskladan accepted D1216: rpm_utils: only support packages in is_installed().
Fri, Jun 30, 1:05 PM

Tue, Jun 27

jskladan accepted D1214: resultsdb_directive: log submitted results.

lgtm

Tue, Jun 27, 3:18 PM
jskladan accepted D1213: Sorting by key plugin for browse results collection.

Looks good. I fixed a non-issue lint error and merged the patch. Thanks!

Tue, Jun 27, 8:25 AM

Mon, Jun 26

jskladan requested changes to D1213: Sorting by key plugin for browse results collection.

Some minor issues, mostly WRT keeping the new code in the same style as the already existing pieces. My only actual functional issue here is that I'd probably just plain allowed _sort to manipulate submit_time - other fields of the Result object are IMO not really that relevant for custom-sorting, and the "exciting" user data (which I suppose could be more interesting to sort by) is stored in ResultData (and this inaccessible by this patch) anyway.

Mon, Jun 26, 2:11 PM

Jun 20 2017

jskladan requested changes to D1196: *WIP* More hacky support, but for containers.

On top of the failing tests, some of which are really weird, I suggest you investigate/fix ASAP, I have some mostly semantical issues.

Jun 20 2017, 3:08 PM · libtaskotron
jskladan accepted D1187: Update template to work regardless of what base url execdb has..

this is fine

Jun 20 2017, 11:31 AM
jskladan added a comment to D1209: ship Alembic migration scripts as package data.

If the rpm builds/installs and migrations keep working, it's fine with me. Have you tried building/installing the package, and running resultsdb [init_alembic, init_db, upgrade_db] commands? I'm not really sure how this works, but it seems like the script_location is a path that needs to work from the location from which the migration is executed. I can see how this works when you run it from inside the repo, but I'm not sure whether this will be the same for the app installed from the package.

Jun 20 2017, 11:30 AM

Jun 19 2017

jskladan accepted D1210: resultsdb_directive: change default log link to artifactsdir.
Jun 19 2017, 12:23 PM

Jun 14 2017

jskladan added a comment to D1206: Add Dockerfile and OpenShift template.

Just fyi - I don't have, and won't have any input, comments on this. Feel free to merge once you decide what you wanna do.

Jun 14 2017, 2:57 PM

Jun 13 2017

jskladan added a comment to D1208: master.cfg for Buildbot and new ExecDB.

will do

Jun 13 2017, 7:49 AM · infrastructure

Jun 12 2017

jskladan added a comment to D1208: master.cfg for Buildbot and new ExecDB.

The patch overrides all the buildsteps we use - since we want every step to report on its progress, we ought to change how they behave, base or not. (I'm not sure I understand what you mean, though).

Jun 12 2017, 2:40 PM · infrastructure
jskladan created D1208: master.cfg for Buildbot and new ExecDB.
Jun 12 2017, 12:46 PM · infrastructure

May 26 2017

jskladan accepted D1191: A stomp messaging plugin..

Who am I to say what works, and what does not :) I guess you tested it with your usecase, so feel free to merge!

May 26 2017, 11:09 AM

May 23 2017

jskladan requested changes to D1196: *WIP* More hacky support, but for containers.

Well, I'm not a huge fan of this - since not all the commands support the --format flag. This will most definitely have the same issues as testcloud does, but if the goal is to really have it now...

May 23 2017, 10:10 AM · libtaskotron
jskladan added a comment to T878: replace depcheck with rpmdeplint.

me likes!

May 23 2017, 9:10 AM · Restricted Project, task-depcheck, Restricted Project, new-check-ideas
jskladan accepted D1195: Support for Ansible Tasks.
  • inner runner :(
May 23 2017, 8:56 AM

May 18 2017

jskladan accepted D1198: change documentation theme.

LG™

May 18 2017, 1:21 PM

May 16 2017

jskladan added a comment to D1196: *WIP* More hacky support, but for containers.

Looks good for a WIP. My concern here is, that with disposable minions, we do a thing where we use "the right fedora version", so e.g. fc24 packages are tested on F24 machine, and so on. I'd like to see the same for Docker - it can even be done quite easily. Not that it needs to happen for PoC, but I'd like at least a big fat "TODO/FIXME" somewhere in the code to remind you of that :)

May 16 2017, 7:19 AM · libtaskotron
jskladan added a reviewer for D1196: *WIP* More hacky support, but for containers: libtaskotron.
May 16 2017, 6:57 AM · libtaskotron
jskladan added a comment to D1195: Support for Ansible Tasks.

Looks good as for a WIP to me. My only real concern here is the broad deletion of all the minion-related code - this might be because I'm not familiar with the design details, but WRT the disposable "minion" - what is the plan for choosing the "right" image for the task (aka using F24 to test F24 packages) that we had in the "previoius" code? Are we dropping the feature alltogether, or is there another process being planned to do that? If so, what is it?

May 16 2017, 6:56 AM

Apr 20 2017

jskladan added a comment to T943: Add basic search functionality to execdb frontend.

What would be the usual search queries?

Apr 20 2017, 2:04 PM · execdb

Apr 3 2017

jskladan added a comment to D1183: changing name of 'branch' parameter so it isn't squashed in buildbot. Fixes T933.

Macro doge: so changes much good very thanks!

Apr 3 2017, 1:47 PM
jskladan accepted D1183: changing name of 'branch' parameter so it isn't squashed in buildbot. Fixes T933.

I'd like to have the task['repo'] changed to task['git_repo'] for the sake of consistency, but it is not a huge issue. Looks good other than this nitpick.

Apr 3 2017, 1:40 PM

Mar 30 2017

jskladan requested changes to D1183: changing name of 'branch' parameter so it isn't squashed in buildbot. Fixes T933.

Apart of the comments below, I'd like to see the testsuite updated to reflect the changes, I don't see how this could pass unittests.

Mar 30 2017, 8:01 AM

Mar 24 2017

jskladan created D1177: Fix default wildcard search in frontend (100x spedup).
Mar 24 2017, 10:15 AM
jskladan accepted D1176: taskformula: replace vars in dictionary keys.

I'd like to see some inline comments, but looks good otherwise

Mar 24 2017, 9:21 AM

Mar 21 2017

jskladan accepted D1171: argparse: change --arch to be a single value instead of a string.

Macro megusta:  me langusta

Mar 21 2017, 1:26 PM
jskladan accepted D1172: yumrepoinfo: specify all primary and alternate arches.
Mar 21 2017, 11:18 AM
jskladan requested changes to D1171: argparse: change --arch to be a single value instead of a string.
Mar 21 2017, 11:17 AM

Mar 14 2017

jskladan accepted D1165: yumrepoinfo: handle alternate arches.
Mar 14 2017, 12:28 PM
jskladan accepted D1164: i386 is now alternate arch since Fedora 26.

Whatevs...

Mar 14 2017, 8:59 AM

Mar 8 2017

jskladan accepted D1160: changing testcase field to 1024.

D1150 will need adjustments, but that's a non issue.

Mar 8 2017, 1:59 PM
jskladan accepted D1159: support multiple builders for tasks stored in distgit. Fixes T925.

Fine with me

Mar 8 2017, 1:58 PM · taskotron-trigger

Mar 3 2017

jskladan retitled D1158: Fix links in job overview from to Fix links in job overview.
Mar 3 2017, 2:49 PM

Feb 23 2017

jskladan retitled D1150: Decouple ExecDB from Buildbot from to Decouple ExecDB from Buildbot.
Feb 23 2017, 12:35 PM
jskladan accepted D1148: docs: add base-design documentation.
Feb 23 2017, 9:02 AM

Feb 22 2017

jskladan edited the content of Execdb Rewrite.
Feb 22 2017, 2:05 PM · execdb
jskladan added a comment to D1136: Report job 'priority' to ResultsDB (T902).

https://pagure.io/fedora-qa/lolz_and_roffle - parses template file from openqa for priorities, and shows whether compose identified by compose id is valid alpha/beta/final and a list of failures in each category. Does what you want, does not need to be updated with tests added to openqa.
The only tricky part is handling different priorities for different composes/images on the same testcases (like i386 failures are all basically marked as optional, and so is anything Atomic now). Also, some of your testcases do not report arch (the upgrades as far as I checked) to resultsdb, but only have 64bit in testcase name - seems like a bug, but it is not really relevant to the current state of things.
Example output: https://paste.fedoraproject.org/paste/ar8ur1Pq5iDT7lmoso~zOF5M1UNdIGYhyRLivL9gydE=
Said tool took about two hours to write, and the worst part was figuring out parsing the perl file, and handling the different priorities you have for the same testcases (so, the actual testplan-management-y stuff). Yay for the mighty resultsdb, I guess..

Feb 22 2017, 12:29 PM

Feb 21 2017

jskladan added a comment to D1136: Report job 'priority' to ResultsDB (T902).

There's no work to be done to 'migrate off' it, you just flip over to using the proper system whenever it actually appears. The value does no-one any harm if it's just sitting there with nothing using it.

Feb 21 2017, 7:58 AM
jskladan added a comment to D1136: Report job 'priority' to ResultsDB (T902).

oh, forgot to mention: I also think that implementing a 'proper system' for this is likely to be quite a lot of work and involve answering some difficult questions, and I think doing a rushed implementation of the 'proper system' is *more* likely to cause long-term pain than just using a dumb stopgap measure for now. The stopgap gives us a bit of breathing room to design the 'proper system' well.

Feb 21 2017, 7:53 AM
jskladan added a comment to D1136: Report job 'priority' to ResultsDB (T902).

Hey, if a system existed I'd be lining up to use it. There just *isn't* one, and I want to be able to put together the 'see if Rawhide is releasable today' workflow without blocking on that for however long it takes to exist.

Nice one, here. You had no problems putting together random scripts in the past... ;)

Feb 21 2017, 7:51 AM
jskladan added a comment to D1136: Report job 'priority' to ResultsDB (T902).

Well, I know I told you this already, but just to reiterate - I do not believe that this is the right place and/or way to store "what is important for this one group" information. The reason being that this is a _policy_ that is by definition _prone to change_. What if there is a decision to change the priority - you can not retrospectively change the values in RDB...
The way to do this is _in a separate system_ - I know you don't like it, and call this a "short term hack" but we all well know that short term hacks have the tendency to stay (and even worse, in this case, also set a standard).
These kind of issues should be handled by an external system, that consumes the raw resutlsdb data, and has the "testplans" (because, honestly, this is nothing more than a poor man's testplan implementation) configured in it.
If it is what it takes, I'm even willing to put together such a tool, that lets you configure what kinds of results, based on metadata (testcase, extradata) are to be taken for, say, "Alpha priority of fedora compose workflow". Thinking about it, we even have a base for that system in the Dashboards.

Feb 21 2017, 7:27 AM

Feb 20 2017

jskladan added a comment to T890: resultsdb_frontend: search is completely broken in production.

Are there issues, still, or are we waiting for the changes to be deployed on all the instances? Dev seems to be working reasonably well for me.

Feb 20 2017, 2:16 PM · Restricted Project, resultsdb
jskladan created Execdb Rewrite.
Feb 20 2017, 10:54 AM · execdb

Feb 16 2017

jskladan accepted D1133: merge two definitions of item types.

LGTM, thanks for taking care of this

Feb 16 2017, 10:02 AM

Feb 14 2017

jskladan added a comment to D1132: URL fix.

Also, could you please, next time, update the one revision you created in the first time, instead of creating new diffs, that are basically the same? Thanks!

Feb 14 2017, 1:41 PM
jskladan added a comment to D1132: URL fix.

I guess this is a new version of D1130? If so, then abandon the D1130 pls.

Feb 14 2017, 1:39 PM

Feb 13 2017

jskladan accepted D1130: Changed URL for migration.

Good catch, thanks.

Feb 13 2017, 2:28 PM
jskladan added a comment to D1129: Migration url fixing.

You could have updated this revision, instead of creating D1130, but I guess Phabricator is a bit complicated for the first time user.
Please abandon this revision (go down to "add comment section" and select "abandon" in the "action" field), so we don't have unnecessary duplicate.
Thanks!

Feb 13 2017, 2:28 PM
jskladan requested changes to D1129: Migration url fixing.
Feb 13 2017, 1:20 PM
jskladan accepted D1127: improve installation and test workflow.

Macro devops:                  iz ok                        I guess...

Feb 13 2017, 1:17 PM
jskladan added inline comments to D1127: improve installation and test workflow.
Feb 13 2017, 12:17 PM

Feb 11 2017

jskladan updated subscribers of T906: Depcheck is crashing with libsolv TB (F25 only?).

How about we just scratch depcheck in favour of rpmdeplint instead? @kparal did some result verifying two weeks back, and it produces the same results as Decheck, while not being a steaming pile of ***. With the added benefit of the testing tool not being "our" code.
I don't see value in trying to make decheck work now, honestly.
Thoughts? @kparal @mkrizek

Feb 11 2017, 9:10 AM · Restricted Project, task-depcheck
jskladan retitled D1128: Make the ExecDB visually more appealing from to Make the ExecDB visually more appealing.
Feb 11 2017, 9:04 AM

Feb 10 2017

jskladan added inline comments to D1127: improve installation and test workflow.
Feb 10 2017, 10:30 PM
jskladan requested changes to D1126: Dockerize taskotron.
Feb 10 2017, 10:18 PM
jskladan accepted D1122: Fix the text in the 'Groups' navigation link.

Cool, thanks. I did not see that page since it was first created :D

Feb 10 2017, 6:39 AM
jskladan added a comment to T904: Taskotron creates huge numbers of ResultsDB groups with duplicate names.

@adamwill absolutely just a courtesy - we are still talking conventions (like "you should provide an item" style convention, maybe, but still a convention), not hard rules, at least in the scope of the actual implementation.
Also, even if this was "the true way", I'd still see a reason to have "I don't care, and just want a random UUID" thing, and the UUID is also a nice identifier, as it has constant length and such things that only really matter for the machines, and humans don't care, but are important anyway.
Good thing about the actual implementation is, that there won't be collisions between the "random" and "specific" UUIDs by definition of how UUIDs work (different namespaces), so you don't even need to be concerned about "random group results" mixing up with the "proper" ones.

Feb 10 2017, 6:27 AM · resultsdb, libtaskotron

Feb 9 2017

jskladan accepted D1120: Improve experience when an optional parameter is not defined on results, groups, and testcases.

Like it, thanks!

Feb 9 2017, 2:18 AM

Feb 8 2017

jskladan added a comment to T904: Taskotron creates huge numbers of ResultsDB groups with duplicate names.

If we're only considering factors like 'not-important-enough-tests', 'dupes' and 'mistakes', I don't think we need to worry about how 'secure' group names or extradata values are. My initial inclination is not to worry about it unless it actually becomes a problem.

Feb 8 2017, 11:38 PM · resultsdb, libtaskotron
jskladan added a comment to D1092: Require at least version 1.3.0 of python-resultsdb_api.

@mprahl can you then please abandon the revision? I could do it for you, but that would mean me commandeering it first, which changes authorship. THanks!

Feb 8 2017, 10:10 AM
jskladan added a comment to D1119: Allow for git_commit type.
In D1119#20856, @kparal wrote:

So how will the item look like?

Feb 8 2017, 9:40 AM
jskladan added a comment to D1119: Allow for git_commit type.
In D1119#20851, @kparal wrote:

Can you explain what this will be used for? Will this cover Pagure/Github/other services?

Feb 8 2017, 9:20 AM
jskladan retitled D1119: Allow for git_commit type from to Allow for git_commit type.
Feb 8 2017, 8:37 AM
jskladan updated the diff for D1110: Rought out the consumer.
  • make it more git source agnostic
  • store server
Feb 8 2017, 8:34 AM · taskotron-trigger
jskladan updated the diff for D1110: Rought out the consumer.
  • lint
Feb 8 2017, 8:24 AM · taskotron-trigger

Feb 7 2017

jskladan added a comment to T904: Taskotron creates huge numbers of ResultsDB groups with duplicate names.
In T904#12930, @kparal wrote:

Well we could make groups follow the same pattern as test cases, so instead of UUIDs we would use unique groups IDs like compose.openqa.Fedora-Rawhide-20170207.n.0 and compose.autocloud.Fedora-Rawhide-20170207.n.0, etc. You could say that if you have the permissions to submit results into dist.depcheck or compose.openqa namespace, you can create a group with the same prefix. If you don't request a specific name, you'll get a random UUID, as currently.

Feb 7 2017, 3:42 PM · resultsdb, libtaskotron
jskladan added inline comments to D1110: Rought out the consumer.
Feb 7 2017, 2:41 PM · taskotron-trigger
jskladan added a project to D1110: Rought out the consumer: taskotron-trigger.
Feb 7 2017, 11:32 AM · taskotron-trigger
jskladan accepted D1117: remove simplejson dep, improve virtualenv and makefile.
Feb 7 2017, 9:16 AM
jskladan added a comment to T904: Taskotron creates huge numbers of ResultsDB groups with duplicate names.

@adamwill thing is, that the group's description is not unique (And IMO should not be), so even though I don't disagree with the need for sensible naming, nor with the fact that searching the names should be possible, I'm pretty certain that direct "all the results in the group with this pretty name" is a good query. The "name" is really just the human-readable description, and the identifier is the UUID.
From my POW, users should not need to query the results by group-name, but by what was tested (I'm open to discussion thought) in the result (item). If a more complex dashboard is needed, it IMO should be another piece of code than resultsdb itself. ResultsDB should stay pretty agnostic to what the data "mean", because once we start to heavily rely on a scheme meaning something, it stops being agnostic, and becomes a targeted solution.
This is once again not disputing the fact, that targeted solutions are great. I just firmly believe that those should be a different system consuming the data from ResultsDB, and presenting them in a more sensible way.
Does this make sense? I'm not absolutely sure we are talking about the same thing here, so I maybe commenting on something completely different than you had in mind.

Feb 7 2017, 8:26 AM · resultsdb, libtaskotron
jskladan requested changes to D1117: remove simplejson dep, improve virtualenv and makefile.

Looks like a wrong version of the diff is uploaded, based on the comment. I'm fine with the changes overall, just make sure this is what you really wanted. (Consider this not a NACK but NEEDS_INSPECTION :) )

Feb 7 2017, 8:20 AM
jskladan accepted D1116: improve testing process.

Awesome, thanks!

Feb 7 2017, 8:13 AM
jskladan accepted D1115: requirements: remove WTForms.

It realy is not required any more. Thanks for catching this.

Feb 7 2017, 8:12 AM
jskladan accepted D1114: improve install and testing process.
Feb 7 2017, 8:11 AM
jskladan added a comment to D1114: improve install and testing process.

Awesome, I like this. Looks like a reasonable middle way to solve the issues.
Thanks a lot for tackling this!

Feb 7 2017, 8:11 AM

Feb 6 2017

jskladan added a comment to D1112: Makefile: don't use system packages when creating virtualenv.

@kparal honestly, at this point, would it not be better, if you just spun-up an 'empty' virtual machine, and figured out all the deps? Not that I have huge issues with polluting my system with random -dev packages (and I sure could figure all of the out on my own, given enough time), but I don't see the benefit, honestly. Let's discuss in qa-devel.

Feb 6 2017, 12:42 PM
jskladan added a comment to D1112: Makefile: don't use system packages when creating virtualenv.

OK, so more into the compilation fun, seems like openssl is missing now:

build/temp.linux-x86_64-2.7/_openssl.c:434:30: fatal error: openssl/opensslv.h: No such file or directory
 #include <openssl/opensslv.h>
                              ^
compilation terminated.
error: command 'gcc' failed with exit status 1
Feb 6 2017, 12:08 PM
jskladan added a comment to D1112: Makefile: don't use system packages when creating virtualenv.

(Reposting the relevant bits of conversation from D1111)

Feb 6 2017, 12:07 PM
jskladan accepted D1111: Makefile: fix `make test`.

Moving the "missing header files and compilation" to D1112, as the removal of --system-site-packages was moved there.
I'll try to repost the relevant comments to D1112.

Feb 6 2017, 12:04 PM
jskladan added a comment to D1111: Makefile: fix `make test`.

Sure can do, but tell me once again, where will the make test actually be used? If it is supposed to be the 'primary' recommended way to run the testsuite for devs, then I'd object, honestly, as I don't see how compiling a bunch of libs is reasonable.

Feb 6 2017, 11:52 AM

Feb 4 2017

jskladan added a comment to D1111: Makefile: fix `make test`.

@kparal maybe even too pristine?

No package 'libffi' found
c/_cffi_backend.c:15:17: fatal error: ffi.h: No such file or directory
 #include <ffi.h>
                 ^
compilation terminated.
Feb 4 2017, 7:57 AM

Feb 3 2017

jskladan added a comment to T904: Taskotron creates huge numbers of ResultsDB groups with duplicate names.

@kparal whatever works for you. I'd rather store the task name, than testcase name, though, as tasks can produce multiple testcases.

Feb 3 2017, 10:40 AM · resultsdb, libtaskotron
jskladan accepted D1113: Phab: enable automatic test suite execution before creating a diff.

Macro devops: blaaargh testing is for babies

Feb 3 2017, 9:56 AM

Feb 2 2017

jskladan added a comment to D1111: Makefile: fix `make test`.

Not commenting on the changes, as I can't get the makefile do what I need anyway. But regarding to the failing test.

Feb 2 2017, 6:40 PM
jskladan added a comment to T904: Taskotron creates huge numbers of ResultsDB groups with duplicate names.

The groups actually are usefull, but I agree that the naming could be better. The thing is, that the group UUIDs are provided by ExecDB, so we can tie the whole execution of a taskotron task together in a sensible way - i.e. all the results from the one taskotron job are in the group.
We sure could name them better (now we just take the task name as the identifier), but it really was not a priority, as the only stuff we really mostly care for is to be able to have a link like this: https://taskotron.fedoraproject.org/resultsdb/results?groups=32682314-e970-11e6-91d5-5254008e42f6 in execdb (the relevant execdb job is here, although the link to results is broken, as I forgot to update it with apiv2.0 in mind: https://taskotron.fedoraproject.org/execdb/jobs/32682314-e970-11e6-91d5-5254008e42f6 )

Feb 2 2017, 6:25 PM · resultsdb, libtaskotron
jskladan added a comment to D1105: Add resultsdb_conventions, module for sharing result conventions.

So now I get to commit without all you darn kids nitpicking my freaking naming schemes. MUAHAHAHAHAHAHA

Feb 2 2017, 3:17 PM
jskladan created Image Macro "devops".
Feb 2 2017, 3:15 PM
jskladan retitled D1110: Rought out the consumer from to Rought out the consumer.
Feb 2 2017, 3:08 PM · taskotron-trigger
jskladan claimed T900: resultsdb_api: test suite is failing.
Feb 2 2017, 12:14 PM · resultsdb
jskladan added a reviewer for D1108: Add OpenID Connect auth module for POST requests: resultsdb.
Feb 2 2017, 11:08 AM · resultsdb