taskotron

#61 Different jobs on dev and stg
Closed: Fixed Opened by mkrizek.

Closed: Fixed
Reopen Issue

In theory, when running same versions of taskotron components, both dev and stg should run same jobs, investigate why there are differencies.

e.g.:

DEV:

libtaskotron results
====================
Generated on: taskotron-dev01.qa.fedoraproject.org
From:         2014-09-18T00:00:01.974491
To:           2014-09-19T00:00:01.974491
Passed: 4948
Failed: 233
Passed checks:
--------------
depcheck: 3109
upgradepath: 1737
rpmlint: 102
Failed checks:
--------------
depcheck: 80
upgradepath: 88
rpmlint: 65

STG:

libtaskotron results
====================
Generated on: taskotron-stg01.qa.fedoraproject.org
From:         2014-09-18T00:00:02.198253
To:           2014-09-19T00:00:02.198253
Passed: 14245
Failed: 458
Passed checks:
--------------
depcheck: 9726
upgradepath: 4346
rpmlint: 173
Failed checks:
--------------
depcheck: 154
upgradepath: 199
rpmlint: 105

rpmlint runs are the same on all instances (dev, stg and prod). depcheck and upgradepath differs in a few runs because they are not run for each item but rather gathered and run after some time expires. Closing.

Metadata Update from @mkrizek:
- Issue tagged with: infrastructure
Metadata
None

infra

None
None
Lowest
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.