QA specific infrastructure
Thu, Jul 13
@mkrizek deployed all to production.
Wed, Jul 12
Josef, can you please deploy the change from D1219 onto taskotron-dev and verify that the config is adjusted properly? Thanks a lot.
Pushed to ansible as 3952106f493.
Tue, Jul 11
Ack. Adding @tflink as a reviewer for more input.
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.
Jun 15 2017
Reassigning back to @tflink for clarification.
Jun 13 2017
Jun 12 2017
Yeah, that answers most of the questions - I just wanted them in the master.cfg file for future reference or if someone is looking at it for the first time
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).
I'd like to see some more comments to describe what's going on and why we're overriding some pretty base buildsteps but other than that, it looks good to me.
Jun 6 2017
Yeah, for some reason, I got it in my head that this was just a CSS problem. Thanks for the correction.
I think we need to solve this for all file types (not just whitelist specific ones), or disable the compression (and use a compressed filesystem or something, if needed). Images still seem broken:
They are served with Content-Type: text/css.
This has been applied in production and seems to be working. Please re-open if the issue shows up again
Jun 2 2017
woot! it works:
Is it mostly css that's the issue? I have an idea for a fix, will see what happens on dev and if it works, will propose as FBR for prod
Can we please disable gzipping everywhere until we have a better solution? Currently even the production reports are broken:
And people start using those.
May 31 2017
This has been pushed to FMN source code and should be deployed once Beta freeze is lifted.
May 26 2017
Pull request here: https://github.com/fedora-infra/fmn/pull/197
May 23 2017
Our documentation links to https://repos.fedorapeople.org/repos/tflink/phabricator/ . I can change that, but kanarip's packages don't work with our Phab instance:
$ arc list Exception [cURL/77] (https://phab.qa.fedoraproject.org/api/user.whoami) <CURLE_SSL_CACERT_BADFILE> The SSL CA Bundles that we tried to use could not be read or are not formatted correctly. (Run with `--trace` for a full exception trace.)
$ arc list --trace ARGV '/usr/share/arcanist/bin/../scripts/arcanist.php' 'list' '--trace' LOAD Loaded "phutil" from "/usr/share/libphutil/src". LOAD Loaded "arcanist" from "/usr/share/arcanist/src". Config: Reading user configuration file "/home/kparal/.arcrc"... Config: Did not find system configuration at "/etc/arcconfig". Working Copy: Reading .arcconfig from "/home/kparal/devel/taskotron/libtaskotron/.arcconfig". Working Copy: Path "/home/kparal/devel/taskotron/libtaskotron" is part of `git` working copy "/home/kparal/devel/taskotron/libtaskotron". Working Copy: Project root is at "/home/kparal/devel/taskotron/libtaskotron". Config: Did not find local configuration at "/home/kparal/devel/taskotron/libtaskotron/.git/arc/config". >>>  <conduit> user.whoami() <bytes = 117> >>>  <http> https://phab.qa.fedoraproject.org/api/user.whoami <<<  <http> 297,727 us <<<  <conduit> 297,936 us
May 22 2017
This is not valid anymore with either kararip's COPR or the packages up for review.
Until the package reviews go through, use kararip's copr. https://copr.fedorainfracloud.org/coprs/kanarip/phabricator/
May 12 2017
Apr 24 2017
'compose' is in the canonical list of accepted types: https://pagure.io/taskotron/libtaskotron/blob/develop/f/libtaskotron/check.py#_244
I'm not exactly sure what the problem is, I didn't know we even use that item type.
Apr 21 2017
Gzipping disabled on dev for the modularity demo next week.
I can confirm this is now working. No need for modularity-testing-framework workaround anymore. Thanks, @puiterwijk!
The fedpkg config change should not be required to work anymore since I have just updated DNS so the internal IP is used for access to pkgs.fp.o, which should resolve this issue in the short term.
After reading the PR response and looking over the bug, I think this will take a longer time to resolve. However, you can do a temporary workaround in modularity-testing-framework - copy the fedpkg config to a temp dir, modify it and then use fedpkg --config. See https://pagure.io/fedpkg/pull-request/120#request_diff to see the necessary changes. I tried it and it works.
It should be solved ideally during Monday 24th.
We will build huge set of modules during Tuesday 25th and testing would go over taskotron.
Apr 20 2017
I've submitted a PR to fix the issue:
Filed issue with fedpkg to fix the problem:
So I fixed it for html. It's not pretty but it should do for this particular use case, for now. Leaving open until I come up with a proper solution.
This will be definitely shown in the next Modularity demo. Sprint #29.
Please fix it asap. We will do hackfest Tue 25 and would be fine to fix the issue before it.
Fix confirmed with depcheck: